Fred2
January 17, 2010, 12:33pm
1
Hi!
Referring to the above subject and having done a bit of research, it
seems this was first reported with wx.python 2.5 on the mailing list
here (in January 2005):
http://aspn.activestate.com/ASPN/Mail/Message/wxpython-users/2296033
and in a bug report here:
http://trac.wxwidgets.org/ticket/2150
The bug report has been closed as duplicate and is referencing another
bug still open on sourceforge here:
http://sourceforge.net/tracker/?group_id=9863&atid=109863&func=detail&aid=1051542
I have tested with wx.python 2.8.10 and I still have the problem.
So where is actually the 'official' bug tracker: trac.wxwidgets.org or
sourceforge.net ?
When can we expect a resolution? Do I need to do anything special to
help out?
Thanks a lot.
Fred
Robin
January 19, 2010, 2:17am
2
Hi!
Referring to the above subject and having done a bit of research, it
seems this was first reported with wx.python 2.5 on the mailing list
here (in January 2005):
ActiveState Community - Boosting coder and team productivity with ready-to-use open source languages and tools.
and in a bug report here:
wxTrac has been migrated to GitHub Issues - wxWidgets
The bug report has been closed as duplicate and is referencing another
bug still open on sourceforge here:
http://sourceforge.net/tracker/?group_id=9863&atid=109863&func=detail&aid=1051542
Here is the trac version of that bug: wxTrac has been migrated to GitHub Issues - wxWidgets . I see that there's now a patch attached there.
I have tested with wx.python 2.8.10 and I still have the problem.
So where is actually the 'official' bug tracker: trac.wxwidgets.org or
sourceforge.net?
Trac. All the bugs were copied from sourceforge a year or two ago, so the text of some of them ended up referring to things in the wrong place.
When can we expect a resolution? Do I need to do anything special to
help out?
If you can do your own wxWidgets/wxPython builds then you can test the patch and provide feedback, etc.
···
On 1/17/10 4:33 AM, Fred wrote:
--
Robin Dunn
Software Craftsman
Fred2
January 19, 2010, 3:02am
3
Hi Robin,
Thanks for the prompt answer and the clarification. I'll try to do that and revert back.
Fred
Robin Dunn wrote:
···
On 1/17/10 4:33 AM, Fred wrote:
Hi!
Referring to the above subject and having done a bit of research, it
seems this was first reported with wx.python 2.5 on the mailing list
here (in January 2005):
ActiveState Community - Boosting coder and team productivity with ready-to-use open source languages and tools.
and in a bug report here:
wxTrac has been migrated to GitHub Issues - wxWidgets
The bug report has been closed as duplicate and is referencing another
bug still open on sourceforge here:
http://sourceforge.net/tracker/?group_id=9863&atid=109863&func=detail&aid=1051542
Here is the trac version of that bug: wxTrac has been migrated to GitHub Issues - wxWidgets . I see that there's now a patch attached there.
I have tested with wx.python 2.8.10 and I still have the problem.
So where is actually the 'official' bug tracker: trac.wxwidgets.org or
sourceforge.net?
Trac. All the bugs were copied from sourceforge a year or two ago, so the text of some of them ended up referring to things in the wrong place.
When can we expect a resolution? Do I need to do anything special to
help out?
If you can do your own wxWidgets/wxPython builds then you can test the patch and provide feedback, etc.
shiva
February 23, 2010, 4:01am
4
the patch seems to solve the rtl bug, but 'Chinese text not wrapped
correctly with wxHtmlWindow'.
regard
Shiva
···
On Jan 19, 10:17 am, Robin Dunn <ro...@alldunn.com> wrote:
On 1/17/10 4:33 AM, Fred wrote:
> Hi!
> Referring to the above subject and having done a bit of research, it
> seems this was first reported with wx.python 2.5 on the mailing list
> here (in January 2005):
>ActiveState Community - Boosting coder and team productivity with ready-to-use open source languages and tools.
> and in a bug report here:
>wxTrac has been migrated to GitHub Issues - wxWidgets
> The bug report has been closed as duplicate and is referencing another
> bug still open on sourceforge here:
>wxWidgets download | SourceForge.net …
Here is the trac version of that bug:wxTrac has been migrated to GitHub Issues - wxWidgets . I see that there's now a patch
attached there.
Robin
March 6, 2010, 7:59am
6
The people who would be able to work on this are not in this group. You'll either need to discuss this on wx-dev, or perhaps just add some comments to the ticket.
···
On 3/5/10 12:00 AM, Frederic Muller wrote:
shiva wrote:
On Jan 19, 10:17 am, Robin Dunn <ro...@alldunn.com> wrote:
On 1/17/10 4:33 AM, Fred wrote:
Hi!
Referring to the above subject and having done a bit of research, it
seems this was first reported with wx.python 2.5 on the mailing list
here (in January 2005):
ActiveState Community - Boosting coder and team productivity with ready-to-use open source languages and tools.
and in a bug report here:
wxTrac has been migrated to GitHub Issues - wxWidgets
The bug report has been closed as duplicate and is referencing another
bug still open on sourceforge here:
wxWidgets download | SourceForge.net …
Here is the trac version of that
bug:wxTrac has been migrated to GitHub Issues - wxWidgets . I see that there's now a
patch
attached there.
the patch seems to solve the rtl bug, but 'Chinese text not wrapped
correctly with wxHtmlWindow'.
regard
Shiva
Thanks a lot Shiva.
So back to my initial question, can someone try to look at that 5 year
old bug regarding Chinese display please? I unfortunately have little to
no programming skills ...
--
Robin Dunn
Software Craftsman