Hi,
I recently discovered leo and decided to give it a try. I'm using the
rst3 plugin for generating latex docs. In general it works like a
charm, but I'm having some problems with the text encoding. The most
annoying one follows. If in my rst tree I've nodes with the character
ŀ (U+0140)
(or
2008/9/15 [EMAIL PROTECTED] [EMAIL PROTECTED]:
1 errors converting Nu?la.
to iso-8859-1
...
The rst-options are:
...
publish_argv_for_missing_stylesheets=--language=ca,--output-
encoding=utf-8,--stylesheet=/home/vmas/.leo/custom_style.sty
Have you tried iso-8859-1 in the
On Sat, Sep 13, 2008 at 11:29 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
Ok, it was indeed as simple as doing:
def mkbutton(text, node_to_push):
ib = c.frame.getIconBarObject()
ib.add(text = text, command = node_to_push.ipush)
Some notes:
- Perhaps stuff like this could be
Hi,
I get the same error using iso-8859-1.
Vicent
On 15 sep, 15:43, Edward K. Ream [EMAIL PROTECTED] wrote:
2008/9/15 [EMAIL PROTECTED] [EMAIL PROTECTED]:
1 errors converting Nu?la.
to iso-8859-1
...
The rst-options are:
...
On Mon, Sep 15, 2008 at 9:12 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I get the same error using iso-8859-1.
I'll look into this. It may be something simple like adding a Python
encoding line somewhere.
Edward
--~--~-~--~~~---~--~~
You received this
On Mon, Sep 15, 2008 at 8:54 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
On Sun, Sep 14, 2008 at 7:40 AM, Kent Tenney [EMAIL PROTECTED] wrote:
I would really like the option for this behaviour:
- Vim plugin active
- click on a node in a @shadow tree
- the FILE opens in Vim, not the node
I use the FileActions plugin to specify that the following code be
executed when a @shadow file node is double clicked. The code
performs the same function that the OpenWith plugin does but it grabs
the derived file instead of the node's contents. This solves part of
your workflow.
Here's how
On Mon, Sep 15, 2008 at 4:54 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
I'm not inclined to do that. It's too specialized. You would bind a
key to read-at-shadow-nodes.
The point is that this kind of specialized feature can easily be done
with @button or @command nodes. I would prefer
Hi again,
*apparently* I've found it. In the rst3.py file I've changed the line
self.initWrite(p,encoding=g.choose(isHtml,'utf-8','iso-8859-1'))
by
self.initWrite(p,encoding=g.choose(isHtml,'iso-8859-1','utf-8'))
and things go fine for me now: the error in the log pane have
disappeared
Hi,
if doesn't matter if I use
@encoding X
or
@rst-options
encoding=X
X in [utf-8, iso-8859-1]
I always get the conversion errors in the log pane.
Vicent.
On 15 sep, 17:44, Edward K. Ream [EMAIL PROTECTED] wrote:
On Mon, Sep 15, 2008 at 10:38 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
On Mon, Sep 15, 2008 at 10:28 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
On Mon, Sep 15, 2008 at 4:54 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
I'm not inclined to do that. It's too specialized. You would bind a
key to read-at-shadow-nodes.
The point is that this kind of specialized
On Mon, Sep 15, 2008 at 1:04 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
if doesn't matter if I use
@encoding X
or
@rst-options
encoding=X
X in [utf-8, iso-8859-1]
I always get the conversion errors in the log pane.
Not surprising, given the value of the encoding argument to
On Mon, Sep 15, 2008 at 11:35 AM, Ed Blake [EMAIL PROTECTED] wrote:
I got the same result as the last poster. Leo is correctly installed in my
Python site packages. Looking at the leo-post-install-script in leo\dist I
see that the registration script has gotten a lot more complicated. It
13 matches
Mail list logo
