Some years ago, I use Thunderbird on FreeBSD, but I'm spanish. Thunderbird on FreeBSD have the "problem" on localization, that doesn't work correctly except changing manually one variable in his configuration.
Plugins like Enigmail works ok with localization, but Lightning seems to be not.
===> The following configuration options are available for thunderbird-24.4.0:
DBUS=on: D-Bus IPC system support
DEBUG=off: Build with debugging support
ENIGMAIL=on: Enigmail extension
GCONF=off: GConf configuration backend support
GIO=on: GIO for file I/O
GNOMEUI=off: libgnomeui support module
GNOMEVFS2=off: GnomeVFS2 (virtual file system) support
GSTREAMER=on: Multimedia support via GStreamer
LIBPROXY=off: Proxy support via libproxy
LIGHTNING=on: Calendar extension
LOGGING=on: Additional log messages
OPTIMIZED_CFLAGS=on: Use extra compiler optimizations
PGO=off: Use Profile-Guided Optimization
PROFILE=on: Build with profiling support
TEST=off: Build and/or run tests
====> Options available for the multi AUDIO: you have to choose at least one of them
ALSA=on: ALSA audio architecture support
PULSEAUDIO=off: PulseAudio sound server support
My actual locale:
(Using UTF-8 as the same)
Over to maintainer (via the GNATS Auto Assign Tool)
With Thunderbird 31 and Lightning 3.3, the problem persist.
As I remember right, lightning is "recreated" at least one time since 2014. So I guess this problem is long solved. (I have thunderbird, but I don't work with lightning).
Question is could this close here?
(In reply to w.schwarzenfeld from comment #4)
Recently updated, the calendar continues on english... now I have Thunderbird 52.5.2 and Lightning 184.108.40.206.
But new problem: I'm trying to remove Lightning for reinstall and now the thunderbird says that the extension is not compatible...
Reading this thread: https://support.mozilla.org/es/questions/1174559
one "patch" is installing "Quick Locale Switcher 2". I will try when this new problem is solved.
(In reply to Toni Ballesta from comment #5)
I had the same problem with 52.7.0.
Reported as bug #227379, with a solution/workaround.
Have you tried that?