thegooglecodearchive / marave

Automatically exported from code.google.com/p/marave
GNU General Public License v2.0
0 stars 0 forks source link

Accents are not displayed properly #33

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Open marave
2. Write something with an accent like "Hola, cómo te va?"

What is the expected output? What do you see instead?
The accent should appear on top of the vocal, insteads appears as a 
different character. The same happens with umlaut (ü).

What version of the product are you using? On what operating system?
Marave 0.4.1 - Ubuntu Karmic Koala

Original issue reported on code.google.com by andresgattinoni on 9 Feb 2010 at 9:44

Attachments:

GoogleCodeExporter commented 9 years ago
Hehe, I meant "vowel" instead of "vocal" :)

Original comment by andresgattinoni on 9 Feb 2010 at 9:46

GoogleCodeExporter commented 9 years ago
Verified. It happens with gtk+ style but not with oxygen, so it seems to fail 
if the 
editor is a QGraphicsWidget instead of a regular QWidget. I knew that would 
break 
stuff :-)

Original comment by roberto.alsina on 9 Feb 2010 at 10:28

GoogleCodeExporter commented 9 years ago
This looks like this  Qtbug: 
http://qt.nokia.com/developer/task-tracker/index_html?
method=entry&id=219928

But... I can't reproduce it in C++ anymore. I need to write some test cases.

Original comment by roberto.alsina on 9 Feb 2010 at 10:44

GoogleCodeExporter commented 9 years ago
Can't reproduce it in a simple PyQt script either, so it seems I must be doing 
something weird.

Original comment by roberto.alsina on 9 Feb 2010 at 10:51

GoogleCodeExporter commented 9 years ago
aha! Try right-alt+a ... I get á that way! 

Original comment by roberto.alsina on 9 Feb 2010 at 10:56

GoogleCodeExporter commented 9 years ago
I get æ

Original comment by andresgattinoni on 9 Feb 2010 at 11:16

GoogleCodeExporter commented 9 years ago
Ok, we probably don't have the exact same keymap

Original comment by roberto.alsina on 9 Feb 2010 at 11:21

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r172.

Original comment by roberto.alsina on 10 Feb 2010 at 12:11

GoogleCodeExporter commented 9 years ago
Sure, it is fixed, I say. I just had to comment a line!

To figure out that was the problem, I had to do the freaking HAL 9000 treatment!

I nullified every method of mainwidget, then commented 95% of the lines in 
mainwidget.__init__ and then when I commented that completely non-threatening 
line... it worked.

Debugging with a magical axe, I call it.

Original comment by roberto.alsina on 10 Feb 2010 at 12:14