[arch-general] "error: unknown encoding UTF8: using iso88591 as fallback"
Hi, for some time past I get error: unknown encoding UTF8: using iso88591 as fallback when running GTK2 and GTK3 apps, Pluma, Claws Mail, Evolution. Other apps, perhaps Qt apps, might be affected too. There are no issues when using those apps, the terminal just shows these messages. [rocketmouse@archlinux ~]$ locale -a C de_DE de_DE@euro de_DE.iso88591 de_DE.iso885915@euro de_DE.utf8 deutsch en_GB en_GB.iso88591 en_GB.utf8 en_US en_US.iso88591 en_US.utf8 german POSIX [rocketmouse@archlinux ~]$ cat /etc/locale.conf LANG=en_US.UTF-8 [rocketmouse@archlinux ~]$ cat ~/.config/locale.conf cat: /home/rocketmouse/.config/locale.conf: No such file or directory [rocketmouse@archlinux ~]$ sudo nano /etc/locale.conf [rocketmouse@archlinux ~]$ cat /etc/locale.conf LANG=en_US.utf8 [rocketmouse@archlinux ~]$ sudo shutdown -r now It doesn't make a difference, I still get the error messages, when running a new session. Regards, Ralf
On 29 May 2015 at 14:19, Ralf Mardorf <ralf.mardorf@rocketmail.com> wrote:
Hi,
for some time past I get
error: unknown encoding UTF8: using iso88591 as fallback
when running GTK2 and GTK3 apps, Pluma, Claws Mail, Evolution. Other apps, perhaps Qt apps, might be affected too.
There are no issues when using those apps, the terminal just shows these messages.
What's the output of just "locale", as the user you have the problem as -- damjan
On Fri, 29 May 2015 14:29:40 +0200, Damjan Georgievski wrote:
On 29 May 2015 at 14:19, Ralf Mardorf <ralf.mardorf@rocketmail.com>
error: unknown encoding UTF8: using iso88591 as fallback
What's the output of just "locale", as the user you have the problem as
[rocketmouse@archlinux ~]$ locale LANG=en_US.utf8 LC_CTYPE="en_US.utf8" LC_NUMERIC="en_US.utf8" LC_TIME="en_US.utf8" LC_COLLATE="en_US.utf8" LC_MONETARY="en_US.utf8" LC_MESSAGES="en_US.utf8" LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL= [rocketmouse@archlinux ~]$
error: unknown encoding UTF8: using iso88591 as fallback
What's the output of just "locale", as the user you have the problem as
[rocketmouse@archlinux ~]$ locale LANG=en_US.utf8 LC_CTYPE="en_US.utf8" LC_NUMERIC="en_US.utf8" LC_TIME="en_US.utf8" LC_COLLATE="en_US.utf8" LC_MONETARY="en_US.utf8" LC_MESSAGES="en_US.utf8" LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL= [rocketmouse@archlinux ~]$
so, your locale is set somewhere else, probablly .profile .bashrc or .xprofile. it seems for these apps it MUST be en_US.UTF-8 - that's the canonical name of the encoding UTF-8 (with the dash). -- damjan
On Fri, May 29, 2015 at 2:38 PM, Damjan Georgievski <gdamjan@gmail.com> wrote:
error: unknown encoding UTF8: using iso88591 as fallback ... it seems for these apps it MUST be en_US.UTF-8 - that's the canonical name of the encoding UTF-8 (with the dash).
I don't think it is locale related, I've used both "en_US.utf8" and "en_US.UTF-8" in the past without issues. And encoding names are used in many other places. My guess is that you have somewhere a XML file with a wrong declaration <?xml version="1.0" encoding="UTF8"?> where the proper declaration would be: <?xml version="1.0" encoding="UTF-8"?> There are some configuration files both in /etc and $HOME that are read upon initialization of Gtk and Qt (see /etc/fonts/*), so I'd check those first: $ grep -ir 'encoding="utf8' /etc $ grep -ir 'encoding="utf8' ~/.config
On 29 May 2015 at 15:02, Rodrigo Rivas <rodrigorivascosta@gmail.com> wrote:
On Fri, May 29, 2015 at 2:38 PM, Damjan Georgievski <gdamjan@gmail.com> wrote:
error: unknown encoding UTF8: using iso88591 as fallback ... it seems for these apps it MUST be en_US.UTF-8 - that's the canonical name of the encoding UTF-8 (with the dash).
I don't think it is locale related, I've used both "en_US.utf8" and "en_US.UTF-8" in the past without issues.
that's half true. glibc normalizes the name of the locale (to lowercase no dashes or underscores - it's a historical thing) so glibc doesn't care. the problem is that some toolkits/apps would extract the charset part of the locale name directly, and not going through the locale functions for that purpose. that has happened in the past, and I wouldn't be supprised if there are toolkits/apps that still do that.
And encoding names are used in many other places.
My guess is that you have somewhere a XML file with a wrong declaration
I haven't seen this, but it's possible. good thing to check.
<?xml version="1.0" encoding="UTF8"?>
where the proper declaration would be:
<?xml version="1.0" encoding="UTF-8"?>
There are some configuration files both in /etc and $HOME that are read upon initialization of Gtk and Qt (see /etc/fonts/*), so I'd check those first:
$ grep -ir 'encoding="utf8' /etc $ grep -ir 'encoding="utf8' ~/.config
-- damjan
On Fri, 29 May 2015 14:38:45 +0200, Damjan Georgievski wrote:
[rocketmouse@archlinux ~]$ locale LANG=en_US.utf8 LC_CTYPE="en_US.utf8" LC_NUMERIC="en_US.utf8" LC_TIME="en_US.utf8" LC_COLLATE="en_US.utf8" LC_MONETARY="en_US.utf8" LC_MESSAGES="en_US.utf8" LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL= [rocketmouse@archlinux ~]$
so, your locale is set somewhere else, probablly .profile .bashrc or .xprofile.
it seems for these apps it MUST be en_US.UTF-8 - that's the canonical name of the encoding UTF-8 (with the dash).
That's the setting I used first. From my first email: [rocketmouse@archlinux ~]$ cat /etc/locale.conf LANG=en_US.UTF-8 Then I edited it: [rocketmouse@archlinux ~]$ sudo nano /etc/locale.conf [rocketmouse@archlinux ~]$ cat /etc/locale.conf LANG=en_US.utf8 However, I can't find anything in $HOME overwriting the settings: [rocketmouse@archlinux ~]$ cat .profile .bashrc .xprofile cat: .profile: No such file or directory # # ~/.bashrc # # If not running interactively, don't do anything [[ $- != *i* ]] && return alias ls='ls --color=auto' PS1='[\u@\h \W]\$ ' export EDITOR="nano" cat: .xprofile: No such file or directory I'm running $ pacman -Q openbox openbox 3.5.2-7 and I don't see anything related in openbox's config, the panel's config gtk2 and 3 and Trolltech configs. I verified [rocketmouse@archlinux ~]$ ls -hAl /etc/locale* -rw-r--r-- 1 root root 16 May 29 14:01 /etc/locale.conf -rw-r--r-- 1 root root 9.1K Feb 17 2013 /etc/locale.gen -rw-r--r-- 1 root root 9.4K Feb 7 10:07 /etc/locale.gen.pacnew Oops, and changed it too [rocketmouse@archlinux ~]$ ls -hAl /etc/locale* -rw-r--r-- 1 root root 16 May 29 14:01 /etc/locale.conf -rw-r--r-- 1 root root 9.4K Feb 7 10:07 /etc/locale.gen -rw-r--r-- 1 root root 9.1K Feb 17 2013 /etc/locale.gen.old I edited the new local.gen and run [rocketmouse@archlinux ~]$ sudo locale-gen Generating locales... de_DE.UTF-8... done de_DE.ISO-8859-1... done de_DE.ISO-8859-15@euro... done en_GB.UTF-8... done en_GB.ISO-8859-1... done en_US.UTF-8... done en_US.ISO-8859-1... done Generation complete. but I got [rocketmouse@archlinux ~]$ locale -a C de_DE de_DE@euro de_DE.iso88591 de_DE.iso885915@euro de_DE.utf8 deutsch en_GB en_GB.iso88591 en_GB.utf8 en_US en_US.iso88591 en_US.utf8 german POSIX "The locale to be used, chosen among the previously generated ones, is set in locale.conf files, each of which must contain a new-line separated list of environment variable assignments, for example:" - https://wiki.archlinux.org/index.php/Locale#Setting_the_locale So no UTF-8 was generated, it's the same as I had before, when neither /etc/locale.conf LANG=en_US.utf8 nor $ cat /etc/locale.conf LANG=en_US.UTF-8 did work. Regards, Ralf
On Fri, 29 May 2015 15:02:16 +0200, Rodrigo Rivas wrote:
My guess is that you have somewhere a XML file with a wrong declaration
<?xml version="1.0" encoding="UTF8"?>
where the proper declaration would be:
<?xml version="1.0" encoding="UTF-8"?>
There are some configuration files both in /etc and $HOME that are read upon initialization of Gtk and Qt (see /etc/fonts/*), so I'd check those first:
[rocketmouse@archlinux ~]$ grep UTF .config/openbox/rc.xml <?xml version="1.0" encoding="UTF-8"?> [rocketmouse@archlinux ~]$ cat .gtkrc-2.0 # Auto-written by gtk2_prefs. Do not edit. gtk-theme-name = "Adwaita" style "user-font" { font_name="FreeSans 12" } widget_class "*" style "user-font" [rocketmouse@archlinux ~]$ cat .config/gtk-3.0/settings.ini [Settings] gtk-theme-name=Adwaita gtk-font-name=FreeSans 12 Neither I see something in the cryptic .config/Trolltech.conf. [rocketmouse@archlinux ~]$ ls -hAld /etc/fonts/* drwxr-xr-x 2 root root 4.0K May 28 21:51 /etc/fonts/conf.avail drwxr-xr-x 2 root root 4.0K May 19 03:19 /etc/fonts/conf.d -rw-r--r-- 1 root root 5.4K Mar 24 2014 /etc/fonts/fonts.conf -rw-r--r-- 1 root root 7.1K Mar 24 2014 /etc/fonts/fonts.dtd drwxr-xr-x 4 root root 4.0K Jun 29 2013 /etc/fonts/infinality I can't see anything related in /etc/fonts/fonts.conf, /etc/fonts/conf.d/50-user.conf, /etc/fonts/conf.avail/51-local.conf, /etc/fonts/conf.avail/50-user.conf What ever I check, e.g [rocketmouse@archlinux ~]$ grep encod .claws-mail/folderlist.xml <?xml version="1.0" encoding="UTF-8"?> or lightdm.conf etc., I can't find something unusual. Regards, Ralf
On Fri, May 29, 2015 at 3:41 PM, Ralf Mardorf <ralf.mardorf@rocketmail.com> wrote:
[rocketmouse@archlinux ~]$ ls -hAld /etc/fonts/* drwxr-xr-x 2 root root 4.0K May 28 21:51 /etc/fonts/conf.avail drwxr-xr-x 2 root root 4.0K May 19 03:19 /etc/fonts/conf.d -rw-r--r-- 1 root root 5.4K Mar 24 2014 /etc/fonts/fonts.conf -rw-r--r-- 1 root root 7.1K Mar 24 2014 /etc/fonts/fonts.dtd drwxr-xr-x 4 root root 4.0K Jun 29 2013 /etc/fonts/infinality
I can't see anything related in /etc/fonts/fonts.conf, /etc/fonts/conf.d/50-user.conf, /etc/fonts/conf.avail/51-local.conf, /etc/fonts/conf.avail/50-user.conf
What ever I check, e.g [rocketmouse@archlinux ~]$ grep encod .claws-mail/folderlist.xml <?xml version="1.0" encoding="UTF-8"?> or lightdm.conf etc., I can't find something unusual.
Note that FontConfig configuration files are actually XML files with extension .conf. Did you look inside all these files? And there are likely other examples of hidden XML files (not related to FC) without the .xml extension. That's why I suggested the commands: $ grep -ir 'encoding="utf8' /etc That will look recursively for any file with the suspicious text.
On Fri, May 29, 2015 at 2:19 PM, Ralf Mardorf <ralf.mardorf@rocketmail.com> wrote:
Hi,
for some time past I get
error: unknown encoding UTF8: using iso88591 as fallback
when running GTK2 and GTK3 apps, Pluma, Claws Mail, Evolution. Other apps, perhaps Qt apps, might be affected too.
There are no issues when using those apps, the terminal just shows these messages.
[rocketmouse@archlinux ~]$ locale -a C de_DE de_DE@euro de_DE.iso88591 de_DE.iso885915@euro de_DE.utf8 deutsch en_GB en_GB.iso88591 en_GB.utf8 en_US en_US.iso88591 en_US.utf8 german POSIX [rocketmouse@archlinux ~]$ cat /etc/locale.conf LANG=en_US.UTF-8 [rocketmouse@archlinux ~]$ cat ~/.config/locale.conf cat: /home/rocketmouse/.config/locale.conf: No such file or directory [rocketmouse@archlinux ~]$ sudo nano /etc/locale.conf [rocketmouse@archlinux ~]$ cat /etc/locale.conf LANG=en_US.utf8 [rocketmouse@archlinux ~]$ sudo shutdown -r now
It doesn't make a difference, I still get the error messages, when running a new session.
Regards, Ralf
I haven't seen you running locale-gen there. Do you expect the reboot to do that? cheers! mar77i
On Fri, 29 May 2015 16:09:27 +0200, Rodrigo Rivas wrote:
$ grep -ir 'encoding="utf8' /etc
[rocketmouse@archlinux ~]$ sudo grep -ir 'encoding="utf8' /etc [rocketmouse@archlinux ~]$ There's nothing.
On Fri, 29 May 2015 17:29:25 +0200, Martti Kühne wrote:
I haven't seen you running locale-gen there. Do you expect the reboot to do that?
Do I have to run local-gen after or before I edit /etc/locale.conf? My understanding is that I have to run locale-gen first and then I need to edit /etc/locale.conf. However, now I run it after editing, resp. it already is UTF-8. [rocketmouse@archlinux ~]$ cat /etc/locale.conf LANG=en_US.UTF-8 [rocketmouse@archlinux ~]$ sudo locale-gen Generating locales... de_DE.UTF-8... done de_DE.ISO-8859-1... done de_DE.ISO-8859-15@euro... done en_GB.UTF-8... done en_GB.ISO-8859-1... done en_US.UTF-8... done en_US.ISO-8859-1... done Generation complete. [rocketmouse@archlinux ~]$ locale -a C de_DE de_DE@euro de_DE.iso88591 de_DE.iso885915@euro de_DE.utf8 deutsch en_GB en_GB.iso88591 en_GB.utf8 en_US en_US.iso88591 en_US.utf8 german POSIX Then I restarted the computer. [rocketmouse@archlinux ~]$ claws-mail selecting folder '#mh/Claws Mail/draft' error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback It's still the same. Regards, Ralf
[rocketmouse@archlinux ~]$ claws-mail
try [rocketmouse@archlinux ~]$ LANG=en_US.UTF-8 claws-mail -- damjan
On Fri, 29 May 2015 18:22:17 +0200, Damjan Georgievski wrote:
[rocketmouse@archlinux ~]$ claws-mail
try [rocketmouse@archlinux ~]$ LANG=en_US.UTF-8 claws-mail
Hi, [rocketmouse@archlinux ~]$ LANG=en_US.UTF-8 claws-mail selecting folder '#mh/Claws Mail/The shared' error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback It has got no side effects, everything is readable. Regards, Ralf
On Fri, May 29, 2015 at 6:30 PM, Ralf Mardorf <ralf.mardorf@rocketmail.com> wrote:
On Fri, 29 May 2015 18:22:17 +0200, Damjan Georgievski wrote:
[rocketmouse@archlinux ~]$ claws-mail
try [rocketmouse@archlinux ~]$ LANG=en_US.UTF-8 claws-mail
Hi,
[rocketmouse@archlinux ~]$ LANG=en_US.UTF-8 claws-mail selecting folder '#mh/Claws Mail/The shared' error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback
It has got no side effects, everything is readable.
Regards, Ralf
Since we ruled out system configuration problems, you will have to look through the files claws-mail would read for input as returned by $ strace -e open -o claws-mail.strace claws-mail When it loads and the error messages are there, you would just quit claws-mail again. My guess is that the problem lies in some gui toolkit configuration file, ~/.* or similar. You'll have to rule out any binary files and grep all plaintext files with this: $ grep -Po '(?<=")[^"]+(?=")' claws-mail.strace | while read file; do [[ -e "$file" ]] && file -b "$file" | grep -q text && grep UTF8 "$file"; done Get all string sequences between double quotes from the claws-mail strace log, check if it exists and is a text file using the libmagic-based file tool, then check if it contains your invalid string. You don't even deserve this solution, and you'll start sprae cheers! mar77i
Fri, 29 May 2015 18:15:58 +0200 Ralf Mardorf <ralf.mardorf@rocketmail.com>:
Do I have to run local-gen after or before I edit /etc/locale.conf? My understanding is that I have to run locale-gen first and then I need to edit /etc/locale.conf.
You only run 'locale-gen' after editing '/etc/locale.gen'. '/etc/locale.conf' has nothing to do with that. --byte
Hi, On Fri, 29 May 2015 20:21:43 +0200, Jens Adam wrote:
Fri, 29 May 2015 18:15:58 +0200 Ralf Mardorf <ralf.mardorf@rocketmail.com>:
Do I have to run local-gen after or before I edit /etc/locale.conf? My understanding is that I have to run locale-gen first and then I need to edit /etc/locale.conf.
You only run 'locale-gen' after editing '/etc/locale.gen'. '/etc/locale.conf' has nothing to do with that.
so regarding this everything I did was correct. On Fri, 2015-05-29 at 19:20 +0200, Martti Kühne wrote:
Since we ruled out system configuration problems, you will have to look through the files claws-mail would read for input as returned by $ strace -e open -o claws-mail.strace claws-mail
When it loads and the error messages are there, you would just quit claws-mail again.
My guess is that the problem lies in some gui toolkit configuration file, ~/.* or similar. You'll have to rule out any binary files and grep all plaintext files with this: $ grep -Po '(?<=")[^"]+(?=")' claws-mail.strace | while read file; do [[ -e "$file" ]] && file -b "$file" | grep -q text && grep UTF8 "$file"; done
I did it for Pluma instead of Claws. The error messages appeared when saving a text. [2]
Get all string sequences between double quotes from the claws-mail strace log, check if it exists and is a text file using the libmagic-based file tool, then check if it contains your invalid string.
I don't understand what to do. However, there is an issue with files that don't exist. [1]
You don't even deserve this solution, and you'll start sprae
I don't understand this either. [rocketmouse@archlinux Desktop]$ grep -Po '(?<=")[^"]+(?=")' pluma.strace | grep config /usr/lib/libfontconfig.so.1 /home/rocketmouse/.config/pluma/accels /home/rocketmouse/.config/dconf/user /usr/share/gtksourceview-2.0/language-specs/pkgconfig.lang /var/cache/fontconfig//3830d5c3ddfd5cd38a049b759396e72e-le64.cache-4 /var/cache/fontconfig//df311e82a1a24c41a75c2c930223552e-le64.cache-4 /var/cache/fontconfig//17090aa38d5c6f09fb8c5c354938f1d7-le64.cache-4 /var/cache/fontconfig//f349e9996a5320f6dd491cedd2b1f964-le64.cache-4 /var/cache/fontconfig//f6b893a7224233d96cb72fd88691c0b4-le64.cache-4 /var/cache/fontconfig//d62e99ef547d1d24cdb1bd22ec1a2976-le64.cache-4 /var/cache/fontconfig//210c0516121708a580e22e6b1f9a103a-le64.cache-4 /var/cache/fontconfig//e83f37fcf327f1deda509da0f6605954-le64.cache-4 /var/cache/fontconfig//a0f105d33f75736c5f51c104a35e7606-le64.cache-4 /var/cache/fontconfig//6ba42ae0000f58711b5caaf10d690066-le64.cache-4 /var/cache/fontconfig//2d31a572ce6667f6a0da9c8dc611898b-le64.cache-4 /var/cache/fontconfig//a1c95d6dfc9a7b34f44445cf81166004-le64.cache-4 /var/cache/fontconfig//8d4af663993b81a124ee82e610bb31f9-le64.cache-4 /var/cache/fontconfig//4b172ca7f111e3cffadc3636415fead9-le64.cache-4 /var/cache/fontconfig//5ca8086aeacc9c68e81a71e7ef846b3b-le64.cache-4 /home/rocketmouse/.config/pango/pangorc /home/rocketmouse/.config/pluma/pluma.ini /home/rocketmouse/.config/user-dirs.dirs /home/rocketmouse/.config/dconf/user /home/rocketmouse/.config/enchant/enchant.ordering /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/gtk-3.0/bookmarks /home/rocketmouse/.config/gtk-2.0/gtkfilechooser.ini /home/rocketmouse/.config/gtk-2.0/gtkfilechooser.ini /home/rocketmouse/.config/gtk-2.0/gtkfilechooser.ini /home/rocketmouse/.config/gtk-2.0/gtkfilechooser.ini /home/rocketmouse/.config/dconf/user /home/rocketmouse/.config/gtk-2.0/gtkfilechooser.ini /home/rocketmouse/.config/gtk-2.0/gtkfilechooser.ini /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/gtk-2.0/gtkfilechooser.ini /home/rocketmouse/.config/gtk-2.0/gtkfilechooser.ini.W8WLZX /home/rocketmouse/.config/gtk-2.0/gtkfilechooser.ini /home/rocketmouse/.config/enchant/enchant.ordering /home/rocketmouse/.config/enchant/en_US.dic /home/rocketmouse/.config/enchant/en_US.dic /home/rocketmouse/.config/enchant/en_US.exc /home/rocketmouse/.config/enchant/en_US.exc /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/pluma/accels /home/rocketmouse/.config/pulse/client.conf /home/rocketmouse/.config/pluma/accels /home/rocketmouse/.config/pluma/pluma.ini.VU7FZX Regards, Ralf [1] [rocketmouse@archlinux Desktop]$ grep utf pluma.strace open("/usr/share/locale/en_US.utf8/LC_MESSAGES/pluma.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/pluma.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/gtk20.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/gtk20.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/gtk20-properties.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/gtk20-properties.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/glib20.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/glib20.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/gtksourceview.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/gtksourceview.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/atk10.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/atk10.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/pulseaudio.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/pulseaudio.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/iso_639.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/iso_639.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/iso_3166.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/iso_3166.mo", O_RDONLY) = -1 ENOENT (No such file or directory) [rocketmouse@archlinux Desktop]$ ls -hAl /usr/share/locale/en_US.*/LC_MESSAGES/pluma.mo ls: cannot access /usr/share/locale/en_US.*/LC_MESSAGES/pluma.mo: No such file or directory [rocketmouse@archlinux Desktop]$ ls -hAl /usr/share/locale/*/LC_MESSAGES/pluma.mo -rw-r--r-- 1 root root 38K May 1 2014 /usr/share/locale/af/LC_MESSAGES/pluma.mo [snip] -rw-r--r-- 1 root root 87K May 1 2014 /usr/share/locale/da/LC_MESSAGES/pluma.mo-rw-r--r-- 1 root root 96K May 1 2014 /usr/share/locale/de/LC_MESSAGES/pluma.mo -rw-r--r-- 1 root root 131K May 1 2014 /usr/share/locale/dz/LC_MESSAGES/pluma.mo -rw-r--r-- 1 root root 121K May 1 2014 /usr/share/locale/el/LC_MESSAGES/pluma.mo-rw-r--r-- 1 root root 86K May 1 2014 /usr/share/locale/en_AU/LC_MESSAGES/pluma.mo -rw-r--r-- 1 root root 50K May 1 2014 /usr/share/locale/en_CA/LC_MESSAGES/pluma.mo -rw-r--r-- 1 root root 86K May 1 2014 /usr/share/locale/en_GB/LC_MESSAGES/pluma.mo -rw-r--r-- 1 root root 139K May 1 2014 /usr/share/locale/en@shaw/LC_MESSAGES/pluma.mo -rw-r--r-- 1 root root 73K May 1 2014 /usr/share/locale/eo/LC_MESSAGES/pluma.mo [snip] -rw-r--r-- 1 root root 84K May 1 2014 /usr/share/locale/zh_TW/LC_MESSAGES/pluma.mo [2] [rocketmouse@archlinux Desktop]$ grep -Po '(?<=")[^"]+(?=")' pluma.strace | while read file; do [[ -e "$file" ]] && file -b "$file" | grep -q text && grep UTF8 "$file"; done [rocketmouse@archlinux Desktop]$ grep -Po '(?<=")[^"]+(?=")' pluma.strace | while read file; do [[ -e "$file" ]] && file -b "$file" | grep -q text && grep utf8 "$file"; done af_ZA.utf8 af_ZA.UTF-8 [snip] da_DK.utf8 da_DK.UTF-8 de_AT.utf8 de_AT.UTF-8 de_CH.utf8 de_CH.UTF-8 de_DE.utf8 de_DE.UTF-8 de_LU.utf8 de_LU.UTF-8 el_GR.utf8 el_GR.UTF-8 en_AU.utf8 en_AU.UTF-8 en_BE.utf8 en_BE.UTF-8 en_BW.utf8 en_BW.UTF-8 en_CA.utf8 en_CA.UTF-8 en_DL.utf8 en_DL.UTF-8 en_GB.utf8 en_GB.UTF-8 en_HK.utf8 en_HK.UTF-8 en_IE.utf8 en_IE.UTF-8 en_IN.utf8 en_IN.UTF-8 en_NZ.utf8 en_NZ.UTF-8 en_PH.utf8 en_PH.UTF-8 en_SG.utf8 en_SG.UTF-8 en_US.utf8 en_US.UTF-8 en_ZA.utf8 en_ZA.UTF-8 en_ZW.utf8 en_ZS.UTF-8 es_AR.utf8 es_AR.UTF-8 [snip] zh_HK.utf8: zh_HK.UTF-8 zh_TW.utf8: zh_TW.UTF-8 zu_ZA.utf8: zu_ZA.UTF-8 univ.utf8: en_US.UTF-8 universal.utf8@ucs4: en_US.UTF-8 <keyword>utf8</keyword>
On Fri, 29 May 2015 20:54:34 +0200, Ralf Mardorf wrote:
Get all string sequences between double quotes from the claws-mail strace log, check if it exists and is a text file using the libmagic-based file tool, then check if it contains your invalid string.
Ok, this is what your command line did. But how to continue?
On Fri, May 29, 2015 at 5:51 PM, Ralf Mardorf <ralf.mardorf@rocketmail.com> wrote:
On Fri, 29 May 2015 16:09:27 +0200, Rodrigo Rivas wrote:
$ grep -ir 'encoding="utf8' /etc
[rocketmouse@archlinux ~]$ sudo grep -ir 'encoding="utf8' /etc [rocketmouse@archlinux ~]$
There's nothing.
Hmmm... what about the other one? $ sudo grep -ir 'encoding="utf8' ~/.config If that fails and you are out of ideas and you have spare time to waste you could also try: $ sudo grep -ir 'encoding="utf8' ~ $ sudo grep -ir 'encoding="utf8' /var/cache
On Fri, 29 May 2015 23:30:47 +0200, Rodrigo Rivas wrote:
Hmmm... what about the other one?
$ sudo grep -ir 'encoding="utf8' ~/.config
No hits.
If that fails and you are out of ideas and you have spare time to waste you could also try:
$ sudo grep -ir 'encoding="utf8' ~
Excepted of bash history and text of email bodies, like the one from your email, also no hits.
$ sudo grep -ir 'encoding="utf8' /var/cache
No hits.
try it with a new user. If it doesn't work there, it's a global thing. If it does, clean your home
On 29/05/15 at 02:35pm, Ralf Mardorf wrote:
On Fri, 29 May 2015 14:29:40 +0200, Damjan Georgievski wrote:
On 29 May 2015 at 14:19, Ralf Mardorf <ralf.mardorf@rocketmail.com>
error: unknown encoding UTF8: using iso88591 as fallback
What's the output of just "locale", as the user you have the problem as
[rocketmouse@archlinux ~]$ locale LANG=en_US.utf8 LC_CTYPE="en_US.utf8" LC_NUMERIC="en_US.utf8" LC_TIME="en_US.utf8" LC_COLLATE="en_US.utf8" LC_MONETARY="en_US.utf8" LC_MESSAGES="en_US.utf8" LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL= [rocketmouse@archlinux ~]$
Hey Ralf, Isn't **utf8** supposed to be **utf-8** ? ``` locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= ``` en_US.utf8 is different than en_US.UTF-8 Cheers
On 30/05/15 at 10:16am, AC wrote:
On 29/05/15 at 02:35pm, Ralf Mardorf wrote:
On Fri, 29 May 2015 14:29:40 +0200, Damjan Georgievski wrote:
On 29 May 2015 at 14:19, Ralf Mardorf <ralf.mardorf@rocketmail.com>
error: unknown encoding UTF8: using iso88591 as fallback
What's the output of just "locale", as the user you have the problem as
[rocketmouse@archlinux ~]$ locale LANG=en_US.utf8 LC_CTYPE="en_US.utf8" LC_NUMERIC="en_US.utf8" LC_TIME="en_US.utf8" LC_COLLATE="en_US.utf8" LC_MONETARY="en_US.utf8" LC_MESSAGES="en_US.utf8" LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL= [rocketmouse@archlinux ~]$
Hey Ralf,
Isn't **utf8** supposed to be **utf-8** ?
```
locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
```
en_US.utf8 is different than en_US.UTF-8
Cheers
My bad, replied without reading what others has suggested you. Can you set the following environment variables in your shell configuration file: export LC_ALL= export LC_COLLATE="C" Does claws has some configuration file where you can explicitly set the charset ? In mutt there are **send_charset** and **charset** variables that let you specify the charset. Cheers
On Sat, 30 May 2015 10:16:59 +0000, AC wrote:
On 29/05/15 at 02:35pm, Ralf Mardorf wrote:
LANG=en_US.utf8 LANG=en_US.UTF-8
$ grep en /etc/locale.gen | grep -v "#" ; grep de /etc/locale.gen | grep -v "#" en_GB.UTF-8 UTF-8 en_GB ISO-8859-1 en_US.UTF-8 UTF-8 en_US ISO-8859-1 de_DE.UTF-8 UTF-8 de_DE ISO-8859-1 de_DE@euro ISO-8859-15 I don't understand why "utf8" is generated on my machine. Regards, Ralf
On 30 May 2015 at 13:03, Ralf Mardorf <ralf.mardorf@rocketmail.com> wrote:
On Sat, 30 May 2015 10:16:59 +0000, AC wrote:
On 29/05/15 at 02:35pm, Ralf Mardorf wrote:
LANG=en_US.utf8 LANG=en_US.UTF-8
$ grep en /etc/locale.gen | grep -v "#" ; grep de /etc/locale.gen | grep -v "#" en_GB.UTF-8 UTF-8 en_GB ISO-8859-1 en_US.UTF-8 UTF-8 en_US ISO-8859-1 de_DE.UTF-8 UTF-8 de_DE ISO-8859-1 de_DE@euro ISO-8859-15
I don't understand why "utf8" is generated on my machine.
I already explained that, glibc *internally* normalizes the charset part of the locale name. (because in the past people would inconsitently use iso88591 iso-8859-1 iso_8859_1 and other combinations thereof) ALWAYS use .UTF-8 when setting up the locale. Can you please also run the command "LANG=en_US.UTF-8 locale" also if "LC_ALL=en_US.UTF-8 claws-mail" still complains the problem is in the application and you should ask upstream. btw, is there any real issue or just the annoying logs? -- damjan
On Sat, 30 May 2015 11:30:19 +0200, Simon Hanna wrote:
try it with a new user. If it doesn't work there, it's a global thing.
Thank you, that's a good hint :). # useradd -m -s /bin/bash mary_jane_doe # passwd mary_jane_doe I'll report back about the adventures of Jane during or after the weekend. Have a good weekend! Ralf PS:
If it does, clean your home
That isn't a good hint ;).
On Sat, 30 May 2015 13:08:26 +0200, Damjan Georgievski wrote:
ALWAYS use .UTF-8 when setting up the locale.
Can you please also run the command
"LANG=en_US.UTF-8 locale"
That's what I did and will do.
also
if "LC_ALL=en_US.UTF-8 claws-mail" still complains the problem is in the application and you should ask upstream.
LC_ALL is on my todo list. It happens to at least Pluma and Evolution too, so it's not related to Claws. On Fri, 29 May 2015 18:30:53 +0200, Ralf Mardorf wrote:
[rocketmouse@archlinux ~]$ LANG=en_US.UTF-8 claws-mail selecting folder '#mh/Claws Mail/The shared' error: unknown encoding UTF8: using iso88591 as fallback
btw, is there any real issue or just the annoying logs?
No, there are no problems, I only experience annoying messages. OTOH if I do real-time recording I dislike useless write access to ~/.xsession-errors, it unlikely will cause problems, but it's a matter of principle. On Sat, 30 May 2015 10:25:09 +0000, AC wrote:
Can you set the following environment variables in your shell configuration file:
export LC_ALL= export LC_COLLATE="C"
As the other hints it's on my todo list. Regards, Ralf
$ LANG=en_US.UTF-8 locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= I'm mistaken, I didn't run this before. Howver, ... $ pluma ** (pluma:1291): WARNING **: Could not load theme icon gtk-home: Icon 'gtk-home' not present in theme (pluma:1291): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed error: unknown encoding UTF8: using iso88591 as fallback [snip] $ LC_ALL=en_US.UTF-8 pluma ** (pluma:1334): WARNING **: Could not load theme icon gtk-home: Icon 'gtk-home' not present in theme (pluma:1334): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed error: unknown encoding UTF8: using iso88591 as fallback [snip]
$ LANG=en_US.UTF-8 locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
I'm mistaken, I didn't run this before.
Howver, ...
$ pluma
** (pluma:1291): WARNING **: Could not load theme icon gtk-home: Icon 'gtk-home' not present in theme
(pluma:1291): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed error: unknown encoding UTF8: using iso88591 as fallback [snip]
$ LC_ALL=en_US.UTF-8 pluma
** (pluma:1334): WARNING **: Could not load theme icon gtk-home: Icon 'gtk-home' not present in theme
(pluma:1334): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed error: unknown encoding UTF8: using iso88591 as fallback [snip]
Hey Ralf, Comment in (#) all ISO-8859-1 locales and leave alone all UTF-8 locales, in /etc/locale.gen type LANG=en_US.UTF-8 as is and run sudo locale-gen , logout & login (kill X), then try running Claws. Cheers
On 30/05/15 at 01:43pm, AC wrote:
$ LANG=en_US.UTF-8 locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
I'm mistaken, I didn't run this before.
Howver, ...
$ pluma
** (pluma:1291): WARNING **: Could not load theme icon gtk-home: Icon 'gtk-home' not present in theme
(pluma:1291): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed error: unknown encoding UTF8: using iso88591 as fallback [snip]
$ LC_ALL=en_US.UTF-8 pluma
** (pluma:1334): WARNING **: Could not load theme icon gtk-home: Icon 'gtk-home' not present in theme
(pluma:1334): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed error: unknown encoding UTF8: using iso88591 as fallback [snip]
Hey Ralf,
Comment in (#) all ISO-8859-1 locales and leave alone all UTF-8 locales, in /etc/locale.gen type LANG=en_US.UTF-8 as is and run sudo locale-gen , logout & login (kill X), then try running Claws.
Cheers
vim just ate the /etc/locale.conf line...
On 30 May 2015 at 13:03, Ralf Mardorf <ralf.mardorf@rocketmail.com> wrote:
On Sat, 30 May 2015 10:16:59 +0000, AC wrote:
On 29/05/15 at 02:35pm, Ralf Mardorf wrote:
LANG=en_US.utf8 LANG=en_US.UTF-8
$ grep en /etc/locale.gen | grep -v "#" ; grep de /etc/locale.gen | grep -v "#" en_GB.UTF-8 UTF-8 en_GB ISO-8859-1 en_US.UTF-8 UTF-8 en_US ISO-8859-1 de_DE.UTF-8 UTF-8 de_DE ISO-8859-1 de_DE@euro ISO-8859-15
I don't understand why "utf8" is generated on my machine.
I already explained that, glibc *internally* normalizes the charset part of the locale name. (because in the past people would inconsitently use iso88591 iso-8859-1 iso_8859_1 and other combinations thereof)
ALWAYS use .UTF-8 when setting up the locale.
Can you please also run the command
"LANG=en_US.UTF-8 locale"
also
if "LC_ALL=en_US.UTF-8 claws-mail" still complains the problem is in the application and you should ask upstream.
btw, is there any real issue or just the annoying logs?
-- damjan
Hey Damjan, The Ralfs problem comes from trying to run two en_US locales but with different encoding and I spotted that. But as you mentioned that glib is involved I did some research and it looks like you and I were correct: https://mail.gnome.org/archives/gnome-hackers/2002-March/msg00253.html Cheers
On Sat, 30 May 2015 13:43:03 +0000, AC wrote:
Comment in (#) all ISO-8859-1 locales and leave alone all UTF-8 locales [...]
Thank you, Done, but unfortunately after sudo locale-gen and a restart nothing's changed. $ pluma ** (pluma:865): WARNING **: Could not load theme icon gtk-home: Icon 'gtk-home' not present in theme (pluma:865): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback ^C $ grep -v "#" /etc/locale.gen de_DE.UTF-8 UTF-8 en_GB.UTF-8 UTF-8 en_US.UTF-8 UTF-8 $ cat /etc/locale.conf LANG=en_US.UTF-8 $ locale -a C de_DE.utf8 en_GB.utf8 en_US.utf8 POSIX I'll test the new user tomorrow. Regards, Ralf
On May 30 2015 19:49, Ralf Mardorf wrote:
error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback error: unknown encoding UTF8: using iso88591 as fallback
It looks like that might be an error from hunspell [1][2]... Are you by chance using a non-standard dictionary?
From my (brief) experimentation, it looks like a malformed affix (.aff) file will cause hunspell to generate that error. (There might be other causes.)
To find suspect system dictionaries: $ find /usr/share/ -name '*.aff' -type f -print0 | xargs -0 grep "UTF8" I don't think hunspell looks in your home directory for affix files, but it wouldn't hurt to also run that command on your home directory. If you find a suspect dictionary (affix file), the top line probably reads "SET UTF8"; change it to "SET UTF-8". (If you got the dictionary from somewhere else, tell them to fix it, too.) See also: hunspell(5), hunspell(1) [1]: https://searchcode.com/?q=%22error%3A+unknown+encoding%22+%22using%22+%22as+... [2]: http://sourceforge.net/p/hunspell/hunspell/ci/master/tree/src/hunspell/csuti... -- Jeffrey Tolar
On Sat, 30 May 2015 15:03:52 -0500, Jeffrey Tolar wrote:
It looks like that might be an error from hunspell
I've got aspell and hunspell installed, but actually it happens when e.g. saveing a file with Pluma, while spell checking wasn't involved. I suspect an inconsistency with the file system. I'll continue tomorrow or on Monday.
On 31/05/15 08:12, Ralf Mardorf wrote:
On Sat, 30 May 2015 15:03:52 -0500, Jeffrey Tolar wrote:
It looks like that might be an error from hunspell
I've got aspell and hunspell installed, but actually it happens when e.g. saveing a file with Pluma, while spell checking wasn't involved. I suspect an inconsistency with the file system. I'll continue tomorrow or on Monday.
Changing UTF8 to UTF-8 in /usr/share/hunspell/en_US.aff fixed that problem in pluma here. Rossco.
I suspect an inconsistency with the file system.
that doesn't make no sense. Unix filesystems don't care about encodings at all. ever -- damjan
On Sun, 31 May 2015 08:22:00 +1200, Ross Hamblin wrote:
Changing UTF8 to UTF-8 in /usr/share/hunspell/en_US.aff fixed that problem in pluma here.
Thank you very much, I edited /usr/share/hunspell/en_CA.aff SET UTF-8 /usr/share/hunspell/en_GB-large.aff SET UTF-8 /usr/share/hunspell/en_US.aff SET UTF-8 and reset my locale $ locale -a C de_DE de_DE@euro de_DE.iso88591 de_DE.iso885915@euro de_DE.utf8 deutsch en_GB en_GB.iso88591 en_GB.utf8 en_US.utf8 german POSIX When I run Pluma and Claws, there is no error output anymore. Regards, Ralf
On Sun, 31 May 2015 04:37:24 +0200, Ralf Mardorf wrote:
On Sun, 31 May 2015 08:22:00 +1200, Ross Hamblin wrote:
Changing UTF8 to UTF-8 in /usr/share/hunspell/en_US.aff fixed that problem in pluma here.
Thank you very much,
I edited
/usr/share/hunspell/en_CA.aff SET UTF-8 /usr/share/hunspell/en_GB-large.aff SET UTF-8 /usr/share/hunspell/en_US.aff SET UTF-8
and reset my locale
$ locale -a C de_DE de_DE@euro de_DE.iso88591 de_DE.iso885915@euro de_DE.utf8 deutsch en_GB en_GB.iso88591 en_GB.utf8 en_US.utf8 german POSIX
When I run Pluma and Claws, there is no error output anymore.
Wow, now several (not all) words can't be written at the beginning of a sentence, if you e.g. start a sentence with the word "Questions", so that you write the first letter upper case, spellchecking marks the word. Questions -> spellchecking claims it's wrong questions -> spellchecking claims it's correct :( IIRC this didn't happened in the past, perhaps my English is that broken, that I begin sentences with words, that never should be used to begin a sentence?! Regards, Ralf PS: "Regards" -> spellchecking claims it's wrong regards -> spellchecking claims it's correct
On Sun, 2015-05-31 at 13:36 +0200, Ralf Mardorf wrote:
Wow,
now several (not all) words can't be written at the beginning of a sentence, if you e.g. start a sentence with the word "Questions", so that you write the first letter upper case, spellchecking marks the word.
Questions -> spellchecking claims it's wrong questions -> spellchecking claims it's correct
:(
IIRC this didn't happened in the past, perhaps my English is that broken, that I begin sentences with words, that never should be used to begin a sentence?!
Regards, Ralf
PS: "Regards" -> spellchecking claims it's wrong regards -> spellchecking claims it's correct
It doesn't happen always, perhaps an issue related to Claws.
Thanks to Jeffrey Tolar too, who was the first who mentions hunspell. Regarding the new issue I sent a mail to the Claws list. http://lists.claws-mail.org/pipermail/users/2015-May/013062.html Regards, Ralf "I" is marked as incorrect, while "i" is correct :D.
Thanks to Jeffrey Tolar too, who was the first who mentions hunspell.
Regarding the new issue I sent a mail to the Claws list. http://lists.claws-mail.org/pipermail/users/2015-May/013062.html
Regards, Ralf
"I" is marked as incorrect, while "i" is correct :D.
Hello Ralf, I'm happy to read that your issue is semi-solved. I like issues that make you tinker, it just proves that when a bunch of people gather together, and make different suggestions, nothing remains 'unsolved'. Cheers
On Sun, May 31, 2015 at 2:53 PM, Ralf Mardorf <ralf.mardorf@rocketmail.com> wrote:
Thanks to Jeffrey Tolar too, who was the first who mentions hunspell.
Regarding the new issue I sent a mail to the Claws list. http://lists.claws-mail.org/pipermail/users/2015-May/013062.html
Regards, Ralf
I've notice from my pacman.log this line: [2015-05-30 19:39] [ALPM] upgraded hunspell-en (7.1-3 -> 2015.05.18-1) Notice the curious change in version number style. I've downgraded to hunspell-en-7.1-3 [1] and it looks fine now. @Ralf: you can try downgrading instead of manually editing the file and see if it fixes the issues. Anyway, I've noticed that besides the wrong encoding, there are some broken symbolic links in that package, so I submitted a bug report to the Arch package [2]. [1]: http://seblu.net/a/arm/packages/h/hunspell-en/hunspell-en-7.1-3-any.pkg.tar.... [2]: https://bugs.archlinux.org/task/45158
On Sun, 31 May 2015 21:20:22 +0200, Rodrigo Rivas wrote:
I've notice from my pacman.log this line:
[2015-05-30 19:39] [ALPM] upgraded hunspell-en (7.1-3 -> 2015.05.18-1)
Notice the curious change in version number style. I've downgraded to hunspell-en-7.1-3 [1] and it looks fine now. @Ralf: you can try downgrading instead of manually editing the file and see if it fixes the issues.
Anyway, I've noticed that besides the wrong encoding, there are some broken symbolic links in that package, so I submitted a bug report to the Arch package [2].
[1]: http://seblu.net/a/arm/packages/h/hunspell-en/hunspell-en-7.1-3-any.pkg.tar.... [2]: https://bugs.archlinux.org/task/45158
Thank you, I also noticed the broken links, but had no time to care about it. $ grep hunspell /var/log/pacman.log | grep 2015 [2015-05-28 19:24] [ALPM] upgraded hunspell-en (7.1-3 -> 2015.05.18-1) [2015-05-31 21:59] [PACMAN] Running 'pacman -U hunspell-en-7.1-3-any.pkg.tar.xz' [2015-05-31 21:59] [ALPM] downgraded hunspell-en (2015.05.18-1 -> 7.1-3) $ grep IgnorePkg /etc/pacman.conf | grep -v "#" IgnorePkg = [snip] hunspell-en Now there are no error messages anymore and I'm allowed to write "Thank you" using upper case. Regards, Ralf
participants (9)
-
AC
-
Damjan Georgievski
-
Jeffrey Tolar
-
Jens Adam
-
Martti Kühne
-
Ralf Mardorf
-
Rodrigo Rivas
-
Ross Hamblin
-
Simon Hanna