* Martin Michlmayr <[EMAIL PROTECTED]> [2007-08-27 17:27]:
> * Berge Schwebs Bjørlo <[EMAIL PROTECTED]> [2006-10-20 02:12]:
> > What's happening with this bug? It seems Python has been patched to
> > fix the problem. Perhaps the bug should be reassigned?
>
> Yeah, it works for me now. I think thi
* Berge Schwebs Bjørlo <[EMAIL PROTECTED]> [2006-10-20 02:12]:
> What's happening with this bug? It seems Python has been patched to
> fix the problem. Perhaps the bug should be reassigned?
Yeah, it works for me now. I think this bug should be closed.
--
Martin Michlmayr
http://www.cyrius.com/
What's happening with this bug? It seems Python has been patched to fix the
problem. Perhaps the bug should be reassigned?
Cheers,
Berge
--
Berge Schwebs Bjørlo
There's an infinite number of monkeys outside who want to talk to us about
this new script for Hamlet that they've worked out.
* "Martin v. Löwis" <[EMAIL PROTECTED]> [2006-02-11 16:58]:
> This bug has now been fixed with the SF patch
>
> http://www.python.org/sf/1428494
>
> which has been committed as revisions r42320 and r42321;
> Debian could probably just copy that code.
doko, can you please review the discussion in
This bug has now been fixed with the SF patch
http://www.python.org/sf/1428494
which has been committed as revisions r42320 and r42321;
Debian could probably just copy that code.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, 10 Feb 2006, "Martin v. L?wis" wrote:
Martin Michlmayr wrote:
Martin, can you please look into this?
Thomas is right: Python sets the locale first to "", then back
to "POSIX". This is intentional: it tries to obtain the CHARSET
during startup, but wants to leave locale control to the
Martin Michlmayr wrote:
> Martin, can you please look into this?
Thomas is right: Python sets the locale first to "", then back
to "POSIX". This is intentional: it tries to obtain the CHARSET
during startup, but wants to leave locale control to the script.
So the test script has a bug: it should
* Thomas Dickey <[EMAIL PROTECTED]> [2006-02-10 06:37]:
> >Right, python Modules/_cursesmodule.c has no explicit support for
> >ncursesw functions.
>
> as noted on the newsgroup discussion this week, python doesn't need
> explicit support for ncursesw functions, but does need a change to its
> set
On Fri, 10 Feb 2006, Peter Samuelson wrote:
[Peter Samuelson]
In the ISO-8859 family, bytes 0x80-0xbf are invalid - and the UTF-8
encoding of "?" is 0xc3 0x84.
Doh! Of course I meant to say bytes 0x80-0x9f are invalid. Anyway,
ncurses seems to reject that same range of bytes even when LC_C
On Fri, 10 Feb 2006, Peter Samuelson wrote:
[Martin v. L?wis]
I also tried compiling/linking with ncursesw instead; this didn't
change anything.
Right, python Modules/_cursesmodule.c has no explicit support for
ncursesw functions.
as noted on the newsgroup discussion this week, python does
[Peter Samuelson]
> In the ISO-8859 family, bytes 0x80-0xbf are invalid - and the UTF-8
> encoding of "Ä" is 0xc3 0x84.
Doh! Of course I meant to say bytes 0x80-0x9f are invalid. Anyway,
ncurses seems to reject that same range of bytes even when LC_CTYPE
indicates UTF-8.
signature.asc
Descrip
[Martin v. Löwis]
> I also tried compiling/linking with ncursesw instead; this didn't
> change anything.
Right, python Modules/_cursesmodule.c has no explicit support for
ncursesw functions.
The reason the python curses code displays "ä" is purely accidental:
python believes it is sending *two*
On Sat, 21 Jan 2006, Martin Michlmayr wrote:
* "Martin v. Löwis" <[EMAIL PROTECTED]> [2006-01-21 08:49]:
I was confused. I didn't wait the three seconds to see the ncurses
actually start.
:/
I also tried compiling/linking with ncursesw instead; this didn't
change anything.
Now that's inte
* "Martin v. Löwis" <[EMAIL PROTECTED]> [2006-01-21 08:49]:
> I was confused. I didn't wait the three seconds to see the ncurses
> actually start.
:/
> I also tried compiling/linking with ncursesw instead; this didn't
> change anything.
Now that's interesting.
Thomas, you promised you'd look in
Martin Michlmayr wrote:
> Strange. What x-terminal-emulator are you using? I normally use
> pterm. I just tried xterm and it in I don't see the bullet at all
> with the Python and I see a ' @ ' in curses.
I was confused. I didn't wait the three seconds to see the ncurses
actually start.
I also
Martin Michlmayr wrote:
> Strange. What x-terminal-emulator are you using? I normally use
> pterm. I just tried xterm and it in I don't see the bullet at all
> with the Python and I see a ' @ ' in curses.
uxterm, from xterm 208-3.1. Locale is set to de_DE.UTF-8.
Regards,
Martin
--
To UNSUBS
* "Martin v. Löwis" <[EMAIL PROTECTED]> [2006-01-21 00:03]:
> > Woo, thanks for the note. I can confirm that this works now - I see
> > the Chinese character too. However, while I can see the umlaut a and
> > the Chinese ren, the bullet is not displayed properly. Do you get
> > this too? Instea
Martin Michlmayr wrote:
> Woo, thanks for the note. I can confirm that this works now - I see
> the Chinese character too. However, while I can see the umlaut a and
> the Chinese ren, the bullet is not displayed properly. Do you get
> this too? Instead of • I see [EMAIL PROTECTED]
I can see th
* "Martin v. Löwis" <[EMAIL PROTECTED]> [2006-01-20 07:33]:
> I just tried to reproduce the problem, with python 2.3.5-9
> and libncurses5 5.5-1, and it just worked. I couldn't try
> the original problem (since I don't know what to use cplay
> for), but in Martin Michlmayrs test case, the bullets d
I just tried to reproduce the problem, with python 2.3.5-9
and libncurses5 5.5-1, and it just worked. I couldn't try
the original problem (since I don't know what to use cplay
for), but in Martin Michlmayrs test case, the bullets display
fine (the Japanese characters show as a dotted box, due
to a
clone 279000 -1
reassign -1 python2.4
severity -1 wishlist
retitle -1 Please provide UTF-8 compliant curses bindings
block 279000 by -1
thanks
This cplay bug is currently waiting for the creation of UTF-8
compliant Python bindings.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE,
On Tue, 19 Jul 2005, Martin Michlmayr wrote:
Has anyone had a chance to look into UTF-8 aware Python bindings for
ncurses?
I meant to do it, but was side-tracked by something else (thanks for the
reminder).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNS
Has anyone had a chance to look into UTF-8 aware Python bindings for
ncurses?
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
* Martin Michlmayr <[EMAIL PROTECTED]> [2005-05-27 08:11]:
> > The script will have to encode the Unicode strings to the locale
> > encoding, e.g. through .encode(locale.nl_langinfo(locale.CODESET)).
>
> But why the script and not the Python binding?
>
> Is there a case where you'd want to .encod
* "Martin v. Löwis" <[EMAIL PROTECTED]> [2005-05-27 07:24]:
> The script will have to encode the Unicode strings to the locale
> encoding, e.g. through .encode(locale.nl_langinfo(locale.CODESET)).
But why the script and not the Python binding?
Is there a case where you'd want to .encode anyting a
On Thu, 26 May 2005, Martin Michlmayr wrote:
* Thomas Dickey <[EMAIL PROTECTED]> [2005-05-26 18:21]:
It's compatible - but bear in mind that strings, e.g., as passed to
addstr() are interpreted based on locale.
What negative effects could that have? Are you thinking of control
characters or
* Thomas Dickey <[EMAIL PROTECTED]> [2005-05-26 18:21]:
> It's compatible - but bear in mind that strings, e.g., as passed to
> addstr() are interpreted based on locale.
What negative effects could that have? Are you thinking of control
characters or anything like that?
Or do you simply mean tha
On Thu, 26 May 2005, Martin Michlmayr wrote:
* Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> [2005-05-26 22:58]:
I think you have to link with ncursesw and call setlocale:
That works. Is ncursesw completely backwards compatible (not on an
ABI level, but API wise)? Or will it break Latin-1 locale
* Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> [2005-05-26 22:58]:
> I think you have to link with ncursesw and call setlocale:
That works. Is ncursesw completely backwards compatible (not on an
ABI level, but API wise)? Or will it break Latin-1 locales?
What is needed to get the Python bindings (i
"Martin v. Löwis" <[EMAIL PROTECTED]>:
> #include
> #include
>
> int main()
> {
> WINDOW *win = initscr();
> waddstr(win, "\303\244\n");
> waddstr(win, "\342\200\242\n");
> waddstr(win, "\344\272\272\n");
> refresh();
> sleep(3);
> endwin(
I have a question about the Python curses bindings and UTF-8 support.
I tried to do my homework but couldn't find a good answer so I'm
asking you. I know that ncurses supports UTF-8 but it seems that the
Python bindings don't, or maybe I have to manually encode UTF-8
strings in some way, but there
Martin Michlmayr wrote:
I received a bug report against cplay (a front-end for audio players
written in Python and using ncurses) that it doesn't support UTF-8.
While trying to solve this problem, the bigger question came up
whether the Python bindings actually support UTF-8.
In Debian, we have a l
Martin,
I received a bug report against cplay (a front-end for audio players
written in Python and using ncurses) that it doesn't support UTF-8.
While trying to solve this problem, the bigger question came up
whether the Python bindings actually support UTF-8.
In Debian, we have a libncurses5 lib
33 matches
Mail list logo
