agen judi bola , sportbook, casino, togel, number game, singapore, tangkas, basket, slot, poker, dominoqq, agen bola
. Semua permainan bisa dimainkan hanya dengan 1 ID. minimal deposit 50.000 ,- bonus cashback hingga 10% , diskon togel hingga 66% bisa bermain di android dan IOS kapanpun dan dimana pun. poker , bandarq , aduq, domino qq , dominobet
. Semua permainan bisa dimainkan hanya dengan 1 ID. minimal deposit 10.000 ,- bonus turnover 0.5% dan bonus referral 20%. Bonus - bonus yang dihadirkan bisa terbilang cukup tinggi dan memuaskan, anda hanya perlu memasang pada situs yang memberikan bursa pasaran terbaik yaitu http://22.214.171.124/
Bola168. Situs penyedia segala jenis permainan poker online kini semakin banyak ditemukan di Internet, salah satunya TahunQQ merupakan situs Agen Judi Domino66 Dan BandarQ Terpercaya
yang mampu memberikan banyak provit bagi bettornya. Permainan Yang Di Sediakan Dewi365 Juga sangat banyak Dan menarik dan Peluang untuk memenangkan Taruhan Judi online ini juga sangat mudah . Mainkan Segera Taruhan Sportbook anda bersama Agen Judi Bola
Bersama Dewi365 Kemenangan Anda Berapa pun akan Terbayarkan. Tersedia 9 macam permainan seru yang bisa kamu mainkan hanya di dalam 1 ID saja. Permainan seru yang tersedia seperti Poker, Domino QQ Dan juga BandarQ Online
. Semuanya tersedia lengkap hanya di ABGQQ. Situs ABGQQ sangat mudah dimenangkan, kamu juga akan mendapatkan mega bonus dan setiap pemain berhak mendapatkan cashback mingguan. ABGQQ juga telah diakui sebagai Bandar Domino Online
yang menjamin sistem FAIR PLAY disetiap permainan yang bisa dimainkan dengan deposit minimal hanya Rp.25.000. DEWI365 adalah Bandar Judi Bola Terpercaya
& resmi dan terpercaya di indonesia. Situs judi bola ini menyediakan fasilitas bagi anda untuk dapat bermain memainkan permainan judi bola. Didalam situs ini memiliki berbagai permainan taruhan bola terlengkap seperti Sbobet, yang membuat DEWI365 menjadi situs judi bola terbaik dan terpercaya di Indonesia. Tentunya sebagai situs yang bertugas sebagai Bandar Poker Online
pastinya akan berusaha untuk menjaga semua informasi dan keamanan yang terdapat di POKERQQ13. Kotakqq adalah situs Judi Poker Online Terpercaya
yang menyediakan 9 jenis permainan sakong online, dominoqq, domino99, bandarq, bandar ceme, aduq, poker online, bandar poker, balak66, perang baccarat, dan capsa susun. Dengan minimal deposit withdraw 15.000 Anda sudah bisa memainkan semua permaina pkv games di situs kami. Jackpot besar,Win rate tinggi, Fair play, PKV Games
This looks like a problem with special characters in a pathname somewhere. Could you describe exactly how OpenSesame is installed, i.e. in which folder? Do you have a username with special characters in it?
Yes, it was username problem. Thank you.
I listed this as an issue, and it should be fixed together with some other Unicode-related problems for the next maintenance release. In the meanwhile, please expose OpenSesame to as many weird characters as possible and inform us about any other problems!
Fyi, you could try the latest pre-release package (currently 0.27.3~pre1), which contains a number of Unicode-related bug-fixes:
Among other things, this should fix the username-issue that you encountered. (If not, please let me know.)
Thank you always for your help.
I met with the same problem of 0.27.2 under Windows XP conditions. I changed the username and installed, but it didnot work. In my case, error is follow,
How can I do to fix?
Unfortunately I coud not access 0.27.3~pre1-win32-1.zip(http://files.cogsci.nl/software/opensesame/pre-releases/opensesame_0.27.3~pre1-win32-1.zip).
Simple changing of username isn't work. I created new user to solve this problem.
By the way I could not access 0.27.3~pre1-win32-1.zip too
It should be accessible now:
Right, that's because Windows doesn't rename the profile folder when the username is changed. And the special characters in the profile folder cause the problem, not the username per se.
This seems to be another issue, but also related to special characters. It probably still persists with 0.27.3~pre1 (but please try and let me know). Does the problem also persist if you create a new Windows account without special characters in it (see above)?
Thank you, sebastiaan and sviter.
1 0.27.3~pre1 did not work under special characters' account, but it works under newly created Windows account without special characters.
2 I could install 0.27.2 through the newly created account and it works. However, 0.27.2 didnot work through the other account.
3 I tried in another Windows XP, which is Japanese characters' account and properly working under Opensesame0.26. In this situation; A) I installed 0.27, before I uninstalled 0.26. In this case, 0.27 could run. If I first uninstalled 0.26 and installed 0.27., I failed to install 0.27. However, once 0.27 has been failed to install, I needed to run the Windows' restoration of the system in order to restore the deleated 0.26.
Sorry for poor explanation.
@sebastiaan By the way, built-in OpenSesame function exp.get_file is also sensitive to nonstandard characters.
Thanks for the feedback! Some Unicode bugs are clearly still in there, but I'm confident we're getting close to the point that OpenSesame will run smoothly on all locales.
One request though: Could you please also post the stacktrace (in case of a runtime error) or contents of
opensesame.exe.log(in case of a failure to start) when reporting an error? Otherwise I cannot tell where the error comes from.
@sebastiaan Sorry, I didn't post stacktrace because it's not a big problem. Just rename files.
I have done some more work to improve support on systems with non-Latin characters. The latest pre-release (0.27.3~pre2) should address many of the issues described above. But, as always, let me know if your experience is otherwise. When reporting problems, please include
opensesame.exe.logand/ or the contents of the debug window.
I have not been able to figure out what the problem was that @Koba reported, so that may or may not still occur.
PS. I have taken the liberty of changing the topic name to reflect that the topic is about Unicode-related problems.
I tried 0.27.3~pre2 on Windows XP . Unfortunately, same as pre1, 0.27.3~pre2 did not work under special characters' account, but it works under the newly created Windows account without special characters. Here is
opensesame.exe.log."line"s have changed a little.
Ok, I think I found the bug responsible. It's a general Python bug: http://bugs.python.org/issue1681974
I just uploaded
0.27.3~pre3, which should work around this issue. However, since I don't experience the bug myself, I cannot test it properly. Please let me know if this resolves the issue for you, in which case I'll release 0.27.3.
0.27.3~pre3is working correctly on systems with Japanese characters.
Thank you so much.
I have a similar issue with Korean characters, but it doesn't have to do with my username or reading in files (so I'm not sure if this is the right thread for this...)
If I have Korean words in a loop (as a variable called 'word') and then I want to, say, display the word in a sketchpad, I should be able to just use "[word]" to get it to show up. From my experience Opensesame is a bit finicky when it comes to getting it to do this.
When I make the sketchpad, I click on the "Ab" button to input text. If I don't do anything special and just enter the font family as "mono" and then input "[word]", all I get is empty boxes instead of text. No surprise there I suppose.
But if when entering the text, if I then click on the font family button, and then under writing systems click on "Korean", then I get a list of Korean fonts. I choose 바탕 (batang), and then input my text. The script looks like this:
This never works, however, and the error I get is:
An unexpected error occurred, which was not caught by OpenSesame. This should not happen! Message:
The resource '바탕.ttf' could not be found in libopensesame.experiment.resource()
Meanwhile, I was able to get the batang.ttf file from a friend. If I do the exact same thing, but then edit the script to say font_family="batang", it works as long as the batang.ttf file is in the same directory as the experiment.
Here's the strange part, which makes me thing there is some bug at work.
If after I've successfully displayed Korean text using font_family="batang", and then on the same sketchpad if I try to input
"[word]" using font_family="mono"(which should display empty boxes), it will work. It's like having Korean text on the sketchpad somehow "cures" it, and now it will display whatever is my loop regardless of the font family. But then if I delete the original line that has the font_family="batang" bit, and now all that's left is the second line that had font_family="mono", it goes back to not working, and just displaying empty boxes.
Has this issue been documented before? As it stands now it can be worked around, but it requires the user to have .ttf files for any Korean (and possible Asian) fonts one wants to use.
And just for reference, I'm running this on Windows 7 under legacy.
Thanks for your feedback! The fact that you have to select a custom font to display particular alphabets is known. It's not really a bug, although it is definitely inconvenient. It is a result from the fact that the font rendering system doesn't automatically select a different font when it encounters a character that is not part of the specified font.
This sounds like there is a problem with locating fonts that have non-latin filenames (issue).
That is very odd indeed. Are you sure that there is no trivial explanation for this? For example, one thing that comes to mind is that you may have placed the Batang font in the filepool under the name
mono.ttf, or something along those lines?
I actually never even put batang.ttf in the file pool. I just leave it in the same directory and it gets detected automatically.