Your message dated Thu, 22 Oct 2015 06:38:02 -0300 with message-id <[email protected]> and subject line No longer an issue since the move to UTF-8 has caused the Debian Bug report #421916, regarding make tuxpaint-config show only available locales as languagues to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 421916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421916 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: tuxpaint-config Version: 0.0.7-1 Severity: grave Justification: renders package unusable Hi there, I dunno if this is a tuxpaint or tuxpaint-config bug, but the contigurations chosen in tuxpaint-config aren't reflected in tuxpaint, even if saved. Example: 1) aptitude install tuxpaint tuxpaint-config 2) run tuxpaint-config 3) choose "Portuguese" as the language 4) run tuxpaint As you can state, the language didn't change. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages tuxpaint-config depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-21 GCC support library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxft2 2.1.8.2-8 FreeType-based font drawing librar ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library tuxpaint-config recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---After testing and finding this is no longer an issue either in jessie or sid, I talked to upstream about whether or not it's still a problem at all. Here's what Pere Pujal i Carabantes said: Tux Paint tries to use the locale corresponding to the requested language, if it fails to load, then it fallbacks to some other UTF-8 locales("en_US.UTF8","en_US.UTF-8","UTF8","UTF-8","C.UTF-8")and tries to show the requested language in the first available UTF-8 locale. If all fallbacks fails then it goes with the plain C locale and in this case I doubt Tux Paint will show correctly many languages. So I think too that this bug no longer applies mainly because C.UTF-8 is generated by default in Debian, but I also think it is worth to keep the FAQ as it is, just in case of a system without UTF-8 locales available. Therefore, I'm closing the bug, as the move to UTF-8 makes it unlikely tuxpaint would fail to start in the right language in all but the most unusual and unlikely circumstances. Ben
--- End Message ---
