News:

cpg1.5.46 Security release - upgrade mandatory!The Coppermine development team is releasing a security update for Coppermine in order to counter recently discovered vulnerabilities. It is important that all users who run version cpg1.5.44 or older update to this latest version as soon as possible.[more]

I noticed that no one is translating finnish... i try to do hard as i can to translate the whole language file... i won't give any times, but you will hear me as i work on it... i need it for my own site and mainly that is the reason i have to translate it...

unable to replicate - for me, the turkish language file is working flawlessly, downloading the package from the server. What section is suppossed to be broken? Actually, the file you submitted is in iso8859-9, while all "true" cpg1.4.x language files are in utf-8 encoding, so I converted the file you submitted in the first place before it went into the package. If you think that you have actually found a bug, start a new thread that discusses this in detail, but I guess you just haven't figured out what utf-8 is and what settings you need to apply in coppermine.

Translations are user contributions. If there is no language file in the package, then nobody has submit it. If you need it that badly, hire someone to do the translation - there's no point in complaining here that no translation has been done - especially if you're a pro (saying that you have a customer makes me think so at least) you should know and understand what open source software is about: it's a community effort!

Line 2073Change it to that name if necessary (leave the numbers).Which name?

I have also converted the file to UTF-8.Should I set $lang_charset to iso-8859-7 or to UTF-8? (Currently I have it to UTF-8 and it works fine).

One thing I found out while testing is that all text/files added before have become unusable; characters appear like questionmarks. But I guess that there is no easy/other way doing this... (or is there?)

One thing I found out while testing is that all text/files added before have become unusable; characters appear like questionmarks. But I guess that there is no easy/other way doing this... (or is there?)

This is not related to translation and has been discussed before. Please don't discuss this in the language thread, it's a support issue.

Yes I know, but I thought I should just let you know...I ran some more tests and the problem persists; files with Greek names are displayed as quotation marks, even if they're added after the switch to the UTF-8 (at the beggining they seem ok).

The translation...The word email was not translated on purpose.For the words browse and screenshot I couldn't find an exact match as well as some of the EXIF terms (such as YCbCrPositioning and Exif Interoperability Offset).