[SL] (no subject)

[<lu...@be...>]

Since version 2.2, I have a problem, which was not present in 2.0.9
(my first experience with SQL-Ledger). The fact is, that creation of
a user is OK (administration login). If I click the user again and
edit something, no error is reported, but a "sql-ledger"
(my database user) password is gone (when I enter again, the field is
empty). Of course no login with that user is possible after. But, if
I type the password again (2nd time I am editing user properties),
the error is reported when I click save (FATAL: Password
authentication failed for user "sql-ledger"). We are
talking about database user password and not sql-ledger user password
all the time! What is interesting is, that even if the error is
reported, everything is saved fine and I can login to the sql-ledger
as this user after. If I enter 'Preferences' now, the same error is
reported every time I save and exit. Even though, all of the
information is accepted and works fine all the time.

I believe this has something to do with caracter sets. I am running
SQL-Ledger on Fedora Core 1 and have chosen also UTF-8 as my
character set in SQL Ledger, since we use a few special characters in
Slovenian language (other possibility would be Central Europe
ISO-8859-2, but I believe everything is going into UTF-8
direction...). I've noticed that files that came with SQL Ledger
installation are ISO-8859-15 encoded (talking about members file and
initially created users.conf files in users dir.), and I've tried to
play changing the encoding of these files (UTF-8 or ISO-8859-15), but
the same is happening all the time... Perl scripts are UTF-8. Is
there anything special I've missed, or my configuration is really so
weird? Otherwise everything seems to be running fine, as much I've
found out until now (but I am still translating everything and
entering accounts, so not very much of the testing has been done
until now). Except a minor annoyance, that decimal signs in
preferences windows for taxes are still english (dots) and not as
everywhere else, but I can live with that without a problem.

And, of course, that the 'all' file structure is slightly changing
with versions, so I have to enter all translations again and again.
Maybe it would be good to create a script which would enable to
import old 'all' file and just correct the new at the end.

If anyone has had similar problems, I'll appreciate any suggestion how to get rid of the annoyances. Otherwise, we have a great program with SQL-Ledger, I believe. I'll
be very happy to contribute with Slovenian adaptation as soon as I have it more or less done (hope to do that during these holidays and in January).


Regards to all,

LUTi

-- 
_______________________________________________
Fill Your Inbox With Beer

Check out the new way better Beer Mail @beer.com
http://mms.beer.com/beermail/