Opened 10 years ago

Last modified 8 years ago

#2554 assigned defect

Accent problem with Write Activity

Reported by: Kacandre Owned by: manuq
Priority: High Milestone: Unspecified
Component: Write Version: Unspecified
Severity: Major Keywords:
Cc: humitos, godiard, uwog Distribution/OS: OLPC
Bug Status: Unconfirmed

Description

Hi SugarLabs team,

We’re deploying 10 XO-1 with os852 and firmware Q2E45 installed.

We’re using the Write Activity build 72 and the standard OLPC US Keyboard.

The problem is the following. The teachers and the kids are writing in Spanish (the XOs have also been tried with the french localization). We usually write an accent like acute or grave using the altgr+3 or 4 after the letter. The accents display ok. The problem with this new version of Sugar is that, when we’re opening a saved text written with Write 72, the accent are replaced by a square with numbers in it.

Hope that my explanations are clear.

Thanks a lot,

Happy new year to the SugarLabs team.

Attachments (5)

Write Activity.odt (2.8 KB) - added by Kacandre 10 years ago.
An example of a file created with the problematic version of Write Activity
write-sentence-to-type.jpeg (10.3 KB) - added by humitos 9 years ago.
This is the sentence to type as example of characters that are not shown in a right way
xo-1.75-us-keyboard.jpeg (220.8 KB) - added by humitos 9 years ago.
I could reproduce this error with this keyboard
Screenshot of _Write Activity_.png (19.5 KB) - added by humitos 9 years ago.
This is how I see the text after resuming Write
abiword-example.abw (2.4 KB) - added by humitos 9 years ago.
File created with AbiWord on XO 1.75 os9

Download all attachments as: .zip

Change History (21)

comment:1 Changed 10 years ago by alsroot

  • Component changed from untriaged to Write
  • Owner set to uwog

comment:2 Changed 10 years ago by uwog

This sounds like a bug in AbiWord's OpenDocument filter.

Would it be possible to provide us an example document that was created in AbiWord (ie. NOT in Write) itself, and saved in the standard .abw format? That would help a lot.

Changed 10 years ago by Kacandre

An example of a file created with the problematic version of Write Activity

comment:3 Changed 10 years ago by Kacandre

I don't understand your request. AbiWord isn't install. However, I've attached an example of a file created with Write using the usual Keep icon. I transferred the .odt from to Journal to an USB stick. I've tried to open it with OpenOffice.org seems there's no problem. But then I've launched it with the Write Activity and observed the same problem with accent grave and acute.

comment:4 Changed 10 years ago by RafaelOrtiz

diagnosing: this seems like a problem of encoding of write when saving, I've opened the attached file with open-office and it tells me that it needs to be fixed, when fixed it displays o.k, but when opened in write it has encoding issues with accents
after resumed.

could be that write is not detecting locale encoding?.

comment:5 Changed 9 years ago by humitos

  • Cc humitos godiard added

Related with: #3609

comment:6 Changed 9 years ago by humitos

I could reproduce this error:

  • XO 1.75 os9
  • Sugar Language: English
  • Keyboard hardware: English (see attached picture)
    • Keyboard Model: OLPC
    • Keyboard Layout(s): English - Default la...lish (US)
    • Key(s) to change layout: Alt+Caps lock

Steps to reproduce this error:

  1. Open Write Activity
  2. Type the sentence that "Kacandre" uploaded (pay attention at the special symbols - you have to open the .odt file to see the properly). I will attach an image just in case. The sentence is something like this:
    À la semaine prochaine ou à l’été prochain François. J’ai hâte à ta fête.
    
  3. Close Write Activity
  4. Open Write Activity again.

Issue:

You will see some strange characters there

Expected behavior:

Show the same characters that I have just typed.

Changed 9 years ago by humitos

This is the sentence to type as example of characters that are not shown in a right way

Changed 9 years ago by humitos

I could reproduce this error with this keyboard

Changed 9 years ago by humitos

This is how I see the text after resuming Write

comment:7 Changed 9 years ago by humitos

  • Cc uwog added

I'm uploading the file that you requested some time ago. I created it with AbiWord included in os9 on XO 1.75.

Hope it helps! :)

Changed 9 years ago by humitos

File created with AbiWord on XO 1.75 os9

comment:8 Changed 9 years ago by humitos

I opened this file in my Debian Testing OS (AbiWord 2.9.2) and I see the characters properly.

comment:9 Changed 9 years ago by humitos

Related with #3609

comment:10 Changed 9 years ago by humitos

I was doing A LOT of tests[1] about this thing and I found that the only problem is when the file is saved as Open Office Document (mime type: application/vnd.oasis.opendocument.text).

In fact, if you write the problematic sentence and export the document to PDF, HTML, RTF or TEXT you can see the sentence properly. So I think the problem is in the abiword widget.

I changed this line to use application/rtf instead and I could resume Write and see the characters properly.

[1] all the tests were done with the same environment than in comment:6:ticket:2554

comment:11 Changed 9 years ago by humitos

As uwog said in comment:2:ticket:2554 it seems to be a problem related with the Open Document filter.

I tested it on Abiword directly:

  1. Open Terminal Activity
  2. Type: abiword. Enter.
  3. Write down the sentence attached here as an image
  4. Save the document as Open Document
  5. Close Abiword
  6. Type: abiword again in Terminal Activity
  7. Go to "File -> Open" menu
  8. Select my document saved just saved

I see the characters in a wrong way. So, this issue is related with Abiword itself and has nothing to do with Write. I will report this bug upstream.

comment:12 Changed 9 years ago by humitos

I have Abiword 2.8.6 in XO 1.75 os11: abiword-2.8.6-17.fc17.armv7hl

comment:14 Changed 9 years ago by humitos

I filled in a ticket on the AbiWord's Bugzilla to let them know about this.

comment:15 Changed 9 years ago by humitos

  • Owner changed from uwog to humitos
  • Status changed from new to accepted

comment:16 Changed 8 years ago by manuq

  • Owner changed from humitos to manuq
  • Status changed from accepted to assigned

http://bugzilla.abisource.com/show_bug.cgi?id=13360#c10

The upstream comment say we should check if our font supports Unicode "Combining
Diacritical Marks".

Note: See TracTickets for help on using tickets.