forum.coppermine-gallery.net

Support => cpg1.4.x Support => Older/other versions => cpg1.4 miscellaneous => Topic started by: younk on February 15, 2006, 09:26:04 pm

Title: Charset Danish lang.
Post by: younk on February 15, 2006, 09:26:04 pm
Hi, i have translated the english lang fil from 1.4 to danish. (i havent translated the admin part, but the rest).

I have a bit problem with the charset.

If i use $lang_charset = 'utf-8'; then my menu look like crap. opsÆtning becomes  Ops洮ing. But the album description is fine. rØdtoppe is still rØdtoppe.

If i use $lang_charset = 'iso-8859-1'; then my men look fine, opsÆtning is sill opsÆtning, but then the album description becomes crap. Rødtoppe becomes rødtoppe.

What do i do now? do i have to chance somthing in the database? Should i use Utf-8 og iso-8859-1?

Thanks in advance!
Title: Re: Charset Danish lang.
Post by: Nibbler on February 15, 2006, 09:27:44 pm
Use utf8. What menu are you talking about ?
Title: Re: Charset Danish lang.
Post by: younk on February 15, 2006, 09:34:20 pm
The menu with search, top rated, albums ect.
also the faq.php look like crap.
Title: Re: Charset Danish lang.
Post by: Nibbler on February 15, 2006, 09:41:25 pm
Make sure you are actually saving the lang file in utf format.
Title: Re: Charset Danish lang.
Post by: younk on February 15, 2006, 10:01:02 pm
If i made it $lang_charset = 'utf-8';

it stille make the same crapy letter.

Have i forgotten to chance something in the lang file?
Title: Re: Charset Danish lang.
Post by: Joachim Müller on February 16, 2006, 09:56:42 am
just changing the content of the variable doesn't actually convert the file from iso8859-1 to utf-8  ;)
There currently is no danish translation available yet afaik, refer to the language thread "[Help wanted]: Translations for CPG1.4.x (http://forum.coppermine-gallery.net/index.php?topic=20355.0)" in the announcements board for details. Just submit your file there, I will convert it for you if you don't know how to accomplish this (as suggested in the translator's guide).

Locking this thread now.