Re: SM-2.53: dateformat

2019-05-10 Thread Frank-Rainer Grahl
Hartmut Figge wrote: > At the moment the future of SM is not clear. The 2.57 may come, but > after that? I may have to cease using SM anyway. For the time being, I > am using private builds which can use Alsa. Since SM-Trunk is no longer > usable I have now switched to 2.53. Yeah. The problem is

Re: SM-2.53: dateformat

2019-05-10 Thread Hartmut Figge
EE: >That should be using whatever format you set up for your operating system. It should and did so in the past. Then the problems began. They are fixed in SM-253 if you are not too blind to find the controls. >Does Linux not have an analog to Control Panel or System Preferences? Hm. On

Re: SM-2.53: dateformat

2019-05-10 Thread EE
Hartmut Figge wrote: Greetings, my 2.53 displays date in the thread pane in this way: 5/8/19 6.21 PM for me in Germany it should be this way: 08.05.19, 18:21 I'm using the same user.js as in my 2.56a1 where the display is as wanted. After asking in a German NG I append my user.js so:

Re: SM-2.53: dateformat

2019-05-10 Thread Hartmut Figge
»Q«: >In , >Hartmut Figge wrote: >> Jim Taylor: >> >I tried to test this for you on my openSUSE LEAP 15.0 system but >> >your build needs glibc 2.27 and I only have 2.26 so it won't run. >> >> Thank you for trying. The result would

Re: SM-2.53: dateformat

2019-05-10 Thread »Q«
In , Hartmut Figge wrote: > Jim Taylor: > > >I tried to test this for you on my openSUSE LEAP 15.0 system but > >your build needs glibc 2.27 and I only have 2.26 so it won't run. > > Thank you for trying. The result would have been

Re: SM-2.53: dateformat

2019-05-09 Thread Hartmut Figge
Jim Taylor: >I tried to test this for you on my openSUSE LEAP 15.0 system but your >build needs glibc 2.27 and I only have 2.26 so it won't run. Thank you for trying. The result would have been interesting. I am using Gentoo, mostly stable, but my glibc is part of stable. hafi@i5-64 ~ $ eix

Re: SM-2.53: dateformat

2019-05-09 Thread Jim Taylor
Hartmut Figge wrote: Hartmut Figge: With ac_add_options --disable-pulseaudio ac_add_options --enable-alsa I have sound in my 2.57. That is fine for a private build, but otherwise... hm. No I have build a 2.57 with these options # ac_add_options --disable-pulseaudio ac_add_options

Re: SM-2.53: dateformat

2019-05-09 Thread Frank-Rainer Grahl
Hartmut Figge wrote: Frank-Rainer Grahl: Alsa is no longer supported. I know that. But as long as there are workarounds... Not sure if they fixed it but with tests enabled (ok they are broken anyway) the compile wouldn't go thru. Interesting. Haven't tested that. The only supported

Re: SM-2.53: dateformat

2019-05-09 Thread Hartmut Figge
Frank-Rainer Grahl: >Alsa is no longer supported. I know that. But as long as there are workarounds... >Not sure if they fixed it but with tests enabled >(ok they are broken anyway) the compile wouldn't go thru. Interesting. Haven't tested that. >The only supported option is ac_add_options

Re: SM-2.53: dateformat

2019-05-09 Thread Hartmut Figge
Don Spam's Reckless Son: >Are you now trying to debug Seamonkey or your Linux setup? I am trying to determine if on a Linux which uses pulseaudio a SM-2.57 built with # ac_add_options --disable-pulseaudio ac_add_options --enable-alsa has a working sound. There should be a lot of such Linuxes

Re: SM-2.53: dateformat

2019-05-09 Thread Frank-Rainer Grahl
Hartmut Figge wrote: Hartmut Figge: With ac_add_options --disable-pulseaudio ac_add_options --enable-alsa I have sound in my 2.57. That is fine for a private build, but otherwise... hm. No I have build a 2.57 with these options # ac_add_options --disable-pulseaudio ac_add_options

Re: SM-2.53: dateformat

2019-05-09 Thread Don Spam's Reckless Son
Are you now trying to debug Seamonkey or your Linux setup? The obvious question being if sound works for other applications. If it's Linux then I think this discussion is now in the wrong place. -- spammus ergo sum, viruses courtesy of https://www.nsa.gov/malware/

Re: SM-2.53: dateformat

2019-05-09 Thread Hartmut Figge
Hartmut Figge: >With > >ac_add_options --disable-pulseaudio >ac_add_options --enable-alsa > >I have sound in my 2.57. That is fine for a private build, but >otherwise... hm. No I have build a 2.57 with these options # ac_add_options --disable-pulseaudio ac_add_options --enable-alsa The entry

Re: SM-2.53: dateformat

2019-05-08 Thread Hartmut Figge
Hartmut Figge: >I'll have to test 2.57 for that. Yes. With ac_add_options --disable-pulseaudio ac_add_options --enable-alsa I have sound in my 2.57. That is fine for a private build, but otherwise... hm. Hartmut ___ support-seamonkey mailing list

Re: SM-2.53: dateformat

2019-05-08 Thread Hartmut Figge
Ray_Net: >intl.locale.matchOS set to false >and I did not know where is LC_MESSAGE >and my user.js contaisn only: ># to minimize disk activities 30 minutes instead of 15 seconds >user_pref("browser.sessionstore.interval", 180); >and my date/time is dd-mm-yy hh:mm >I think that I am under

Re: SM-2.53: dateformat

2019-05-08 Thread Hartmut Figge
Frank-Rainer Grahl: >This is exposed in the 2.53 preferences under Apperance -> Date and Time >Formatting. Tested in a new profile. You are right and I am blind. Hartmut ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org

Re: SM-2.53: dateformat

2019-05-08 Thread Hartmut Figge
Frank-Rainer Grahl: >Needs pulseaudio for sure. No. Needs ac_add_options --disable-pulseaudio ac_add_options --enable-alsa I'll have to test 2.57 for that. Hartmut ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org

Re: SM-2.53: dateformat

2019-05-08 Thread Frank-Rainer Grahl
Needs pulseaudio for sure. Hartmut Figge wrote: Works. Now to the problem of no sound in 2.53. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM-2.53: dateformat

2019-05-08 Thread Frank-Rainer Grahl
This is exposed in the 2.53 preferences under Apperance -> Date and Time Formatting. I am not sure if 2.56a1 had all the patches for the new intl api already backported. I doubt it. 2.53 should be fine. I picked everything I found from TB and Gecko up to 60. 2.57 has another l10n problem

Re: SM-2.53: dateformat

2019-05-08 Thread Ray_Net
Hartmut Figge wrote on 08-05-19 20:39: Hartmut Figge: Seems to be a problem with the localization. Or I am mising something. What to do? Bug? I just remembered this problem happened some time ago on Trunk.

Re: SM-2.53: dateformat

2019-05-08 Thread Hartmut Figge
Hartmut Figge: >Seems to be a problem with the localization. Or I am mising something. >What to do? Bug? I just remembered this problem happened some time ago on Trunk. http://reusenet.froehlich.priv.at/posting.php?msgid=8993442e-de1a-a269-5a88-904a98f58...@hfigge.myfqdn.de Sorry, in German.

SM-2.53: dateformat

2019-05-08 Thread Hartmut Figge
Greetings, my 2.53 displays date in the thread pane in this way: 5/8/19 6.21 PM for me in Germany it should be this way: 08.05.19, 18:21 I'm using the same user.js as in my 2.56a1 where the display is as wanted. After asking in a German NG I append my user.js so: