UTF-8 charset directadmin frontend

E

erohas

Verified User
Joined
Aug 5, 2007
Messages
40
Location
Kazakhstan, Almaty
Please add UTF-8 charset by default into Directadmin frontend
because mailing (in|out) to users in native lang via ticket system fails (???? that chars displayed) and for customizing skins it will be useful too

thanks
 
Hello,

For any non-english languages, in the language pack, you can edit:
/usr/local/directadmin/data/skins/enhanced/lang/en/lf_standard.html

this bit:

LANG_ENCODING=iso-8859-1

can be changed to whichever charset you'd like.


As for changing the default, we can look into it.. we'd just need to know that it wouldn't break anything that is already working fine. So maybe give the encoding change to utf-8 a try, then just let us know if you run into any problems or not.

John
 
Yes, it will be very useful to have ability set charset for outgoing DA e-mails (mail notifications), because we have problem with e-mail software (Outlook, Outlook Express, Thunderbird) that can't successfully autodetect UTF-8 in this messages and there's no charset line in mail headers at all.
 
MtK said:
this might be an old post (very), and nice to have utf mails, but you're missing the big picture.
how about having the internal DB (the one that saves all the system settings) in UTF?
Click to expand...
could some1 please address this issue?
 
Hello,

DirectAdmin will save whatever it's given.
What's given to DA is whatever the characterset the skin is set to.
If you change the characterset of the skin to UTF-8, then any settings saved into DA will be UTF-8.

This is related (similar to above) regarding changing to UTF-8 in the skins:
http://help.directadmin.com/item.php?id=35 (very bottom)

John
 
thanks, that solved the problem.

is there a reason why DA is not UTF by default?
 
Hello,

Because we didn't start with it. We're not able to change it now, because anyone who loads existing data will have the wrong format for their data. If we were to start over, I would probably use UTF-8.

John
 
you won't be the first to create a migration tool for that (but It'll be bad if you'll be the last).

anyway, the migration from most Latin languages is really easy, and as you mentioned it's just a changed in the template.
(after all, you also said the DB is already UTF)
 
DirectAdmin Support said:
Hello,

Because we didn't start with it. We're not able to change it now, because anyone who loads existing data will have the wrong format for their data. If we were to start over, I would probably use UTF-8.

John
Click to expand...
bumping into this issue again:
why isn't the installed creating a full UTF language?
(for now, leave updates in your not-utf encoding)
 
You must log in or register to reply here.
Back
Top