Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16930 - [abiword] Non-ASCII characters displayed incorrectly in GUI under UTF-8 locale

Attached to Project: Arch Linux
Opened by Eivind (mokkurkalve) - Friday, 30 October 2009, 20:30 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 27 January 2014, 19:04 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After upgrading to abiword 2.8.1 the menus and other parts of the interface don't show non-ASCII chars correctly in the menus or other parts of the interface anymore. In the document itself it's OK. This is a regression from the 2.6.x series before. I'm using nb_NO.UTF-8 locale and as can be seen in the screenshot the spesific norwegian letters as typed in the document don't display correctly in the GUI. It looks as UTF-8 read as ISO-8859-1 maybe? I don't know, so in this case a screenshot will be the best explaination. Attached.

Additional info:
* package version(s)
abiword 2.8.1-1
* config and/or log files etc.


Steps to reproduce:
   abiword_menu_errors.png (41.5 KiB)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Monday, 27 January 2014, 19:04 GMT
Reason for closing:  Fixed
Comment by Giovanni Scafora (giovanni) - Saturday, 31 October 2009, 07:25 GMT
I do not use nb_NO.UTF-8 locale, so I cannot reproduce that on my system.
Comment by Eivind (mokkurkalve) - Saturday, 31 October 2009, 07:53 GMT
No, I guess most people don't... ;)
But it could be intresting to know if this affects users of other non-english languages using UTF-8 locales as well...
I do have a few applications on this box, and none other have shown this behaviour. Neither did abiword until the 2.8.1 upgrade.
I'm using LXDE/Openbox for graphical environment BTW. Arch linux current and updated (but no testing repo) on i686.
Comment by Giovanni Scafora (giovanni) - Saturday, 31 October 2009, 08:02 GMT
Could you rebuild abiword-2.8.1-1 on your system?
After, you can tell me if abiword works fine or not.
Comment by Giovanni Scafora (giovanni) - Saturday, 31 October 2009, 09:47 GMT
I've just rebuilt abiword setting up nb_NO.UTF8 on my system, but the menus and other parts of the interface don't show non-ASCII chars correctly.
I guess that is an abiword bug, so you should advice the abiword team.
Moreover, I cannot find a patch to solve this issue yet.
Comment by Alessandro Doro (adoroo) - Saturday, 31 October 2009, 15:03 GMT
$ head -1 /usr/share/abiword-2.8/nb-NO.strings
<?xml version="1.0" encoding="ISO-8859-1"?>

The actual file encoding is utf-8.
Comment by Eivind (mokkurkalve) - Saturday, 31 October 2009, 16:12 GMT
Just for testing I buildt abiword locally. Didn't change nothing here either. Also I now tried other locales I have available; de_DE.UTF-8 (german) and nn_NO.UTF-8 (norwegian nynorsk). The problem seems limited to nb_NO.UTF-8 (norwegian bokmål). The other tested locales showed non-english chars like ö ü ß æ ø å correctly. Well, the problem must anyway be upstream. I can use LANG="nn_NO.UTF-8" abiword as a workaround for now. Will report bug to abiword devs soon. Thanks! :)
Comment by Alexander F. Rødseth (xyproto) - Wednesday, 11 September 2013, 17:30 GMT
  • Field changed: Percent Complete (100% → 0%)
This is still a problem. Please use a quick sed command in the PKGBUILD while we are waiting for upstream to fix this.
Comment by Alexander F. Rødseth (xyproto) - Sunday, 17 November 2013, 18:17 GMT
sed 's/ISO-8859-1/UTF-8/' -i /usr/share/abiword-2.8/nb-NO.strings should do the trick (or the path to the correct file in $srcdir if in the PKGBUILD)
Comment by Alexander F. Rødseth (xyproto) - Sunday, 17 November 2013, 18:17 GMT
Assigned to last packager, since abiword is now an orphan.
Comment by Andreas Radke (AndyRTR) - Sunday, 26 January 2014, 14:39 GMT
Is this still an issue with Abiword 3.0 release?
Comment by Alexander F. Rødseth (xyproto) - Monday, 27 January 2014, 18:31 GMT
Works perfectly fine with 3.0!

Loading...