[wxPython-users] wxPython 2.8 RC - Call for testers! :-)

[Kevin Ollivier]

Hi David,

On Dec 1, 2006, at 12:23 PM, David Woods wrote:

> I've done some preliminary testing of the Nov. 29, 2006 wxPython  
> 2.8 Release Candidate with Transana, and found only one problem.  I  
> tested the unicode version on Windows, on OS X 10.3 on a PPC Mac,  
> and on OS X 10.4 on an Intel Mac.
>
> It properly supports all of the video formats I had trouble with in  
> the wxPython 2.7 line with no difficulty.  Thank you for all the  
> work you did to fix that.
>
> I've had unicode problems with the StyledTextCtrl for a number of  
> wxPython versions, as I've reported here before.  The attached code  
> runs okay on Windows, with the exception of Korean characters,  
> which show up in wx.StaticText but not in wx.STC except when mixed  
> on the same line with Chinese characters.  I don't think this has  
> changed in the last several wxPython versions.
>
> On OS X 10.3, under wxPython 2.6.3.2-unicode, accented European  
> characters show up fine, but Chinese, Japanese, and Korean  
> characters cause whole lines of text to disappear, even English  
> text on mixed-language lines.  Unfortunately, a number of common  
> (at least in Transana) characters, such as the character Word for  
> Mac uses as the ellipsis, also cause this problem, so when a user  
> imports a document from Word, I have to scan it for problematic  
> characters.  While the Asian language characters show the problem  
> most easily, the non-text (special character) problems are what  
> have caused me the most headaches.  I can say I don't support  
> Chinese, etc. on the Mac.  I can't say I don't support the  
> ellipsis, the time code, the Euro symbol, and other characters I'm  
> not aware of, especially when I'm trying to allow users to import  
> documents.
>
> On OS X 10.3, under wxPython 2.8.0.0-unicode (RC 20061129), I get  
> the following error message:
>
> wx._core.PyAssertionError: C++ assertion "status == noErr" failed  
> at ../src/mac/carbon/font.cpp(366) in MacFindFont(): couldn't  
> modify ATSU style
>
> This is NOT an improvement, though I wonder if this is at least an  
> indication that the underlying problem is being trapped now.  If  
> so, I can adapt to that.
>
> I haven't tested this on the OS X 10.4 Intel-Mac, as I don't have  
> the appropriate languages installed on that computer.  However, I  
> did see this same error message when importing a transcript the  
> other day, so I'm betting the issue is the same there.

Yes, it happens on 2.8 too, but I think I've found a fix. Try  
removing the single quotes around the face name. The issue is that  
quotes are not stripped from the values, so instead of looking for  
the Times New Roman font, it's looking for 'Times New Roman' instead,  
which it can't find and so it bails out with an error. Same with  
Arial. Once I remove the single quotes, at my end, everything loads  
up just fine.

Please let us know if you come across anything else, and thanks for  
your help! :-)

Regards,

Kevin

> I'll keep using 2.8.0.0-unicode and will let you know if I run into  
> any other problems.
>
> David Woods, Ph.D.
> Transana Lead Developer
> Wisconsin Center for Education Research
> University of Wisconsin, Madison
> http://www.transana.org
>
>
>
> <UnicodeSTC4.py>
>
>
>
>
>
> On Nov 30, 2006, at 6:38 PM, Kevin Ollivier wrote:
>
>> Hi all,
>>
>> Robin made an announcement about the upcoming release of wxWidgets  
>> 2.8 next week on wxpython-dev, but I thought that 2.8 Release  
>> Candidate (RC) testing merited an extra call for help on wxPython- 
>> users as well.
>>
>> So, if you're good at making programs crash, implode, or otherwise  
>> freak out, we need your help! :-) We're on the last stretch for  
>> 2.8, and particularly as it is going to be included in the default  
>> install of OS X 10.5, Leopard, we'd like it to be as solid and  
>> slick as possible. So if you have apps, frameworks, scripts, or  
>> one-liners written using wx, we would appreciate any time you  
>> could spend testing them with the 2.8 RC. Even if it's just 15  
>> minutes, or with one script, or testing the demo... every little  
>> bit helps. We probably won't get to everything reported before the  
>> release, but it's better to find all the issues we can, so we can  
>> at least prioritize and fix the really nasty ones.
>>
>> Oh, and if you don't mind fixing bugs too, well, I promise we  
>> won't complain! :-)
>>
>> The wxPython 2.8 RC can be found here:
>>
>> http://wxpython.wxcommunity.com/preview/20061129/
>>
>> Thanks!
>>
>> Kevin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wxPython-users- 
>> unsubscribe at lists.wxwidgets.org
>> For additional commands, e-mail: wxPython-users- 
>> help at lists.wxwidgets.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wxPython-users-unsubscribe at lists.wxwidgets.org
> For additional commands, e-mail: wxPython-users- 
> help at lists.wxwidgets.org