[Help wanted]: Translations for CPG1.4.x - Page 11 [Help wanted]: Translations for CPG1.4.x - Page 11
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

[Help wanted]: Translations for CPG1.4.x

Started by Joachim Müller, July 04, 2005, 10:05:27 AM

Previous topic - Next topic

0 Members and 3 Guests are viewing this topic.

pcotter

Portuguese translation
Well GauGau, still working on it... Unfortunaly dont have the desired available time!!! :(
Dum Spiro, Spero
http://foto.pcotter.com

katip2000

Hi,
I have translated the first complete translation of Coppermine 1.4  in Tukish language and have included it here.

;)

bikenewyear

I wanted to make the translation, but now I don't have time for it. I have approximately 5-10% of the translation ready. Sorry for not doing it. If anyone need it, email me at ccsabi@netposta.net

Erqe

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...

--- finnish translation work in progress ---

Teune

No translation into Thai for 1.4.x?
I see there was one done for 1.3.2
I have a Thai customer.

Ed
Check out my Bird Photo gallery
http://www.chicagobirds.com

katip2000

Hi.

Turkisch language file is corrupted in 1.44.

I send a new working file here. Please don`t save it again in your PC. Probable your notepad can`t save foreign karakters of Turkisch language.

Joachim Müller

Quote from: katip2000 on March 01, 2006, 07:22:22 PM
Turkisch language file is corrupted in 1.44.
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.


Quote from: Teune on March 01, 2006, 04:22:46 PMNo translation into Thai for 1.4.x?
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!


Quote from: bikenewyear on February 22, 2006, 04:13:23 PM
I wanted to make the translation, but now I don't have time for it. I have approximately 5-10% of the translation ready. Sorry for not doing it. If anyone need it, email me at ccsabi@netposta.net
Why don't you just zip what you have and attach it here instead of making people send an additional email?

Nakis

Hello there again

I have finished the Greek translation but I need to clarify a few issues before I post it...

Line 1380
'err_no_alb_to_modify' => 'No album you can modify in the database.',

Does this mean that there is no album to modify or that you don't have permission to modify?

Fields of the user registration form:
Location
Interests
Website
Occupation
Biography

I didn't find these fields anywhere so they weren't translated.


Line 2073
Change 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?)


Regards
Nakis

Joachim Müller

Quote from: Nakis on March 02, 2006, 03:27:58 PM
Line 1380
'err_no_alb_to_modify' => 'No album you can modify in the database.',

Does this mean that there is no album to modify or that you don't have permission to modify?
both

Quote from: Nakis on March 02, 2006, 03:27:58 PM
Fields of the user registration form:
Location
Interests
Website
Occupation
Biography

I didn't find these fields anywhere so they weren't translated.
Those are special fields that appear only when enabled in coppermine's config - you should translate them.

Quote from: Nakis on March 02, 2006, 03:27:58 PM
Line 2073
Change it to that name if necessary (leave the numbers).

Which name?
cpg_###.reg

Quote from: Nakis on March 02, 2006, 03:27:58 PMI 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).
The file will go into the package as utf-8, but either way is fine: as suggested in the translator's guide, I will convert the language contributions if necessary. Either way is fine.

Quote from: Nakis on March 02, 2006, 03:27:58 PMOne 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?)
charsetmgr.php

Ccecil

new czech.php version 1.20

modify problem Galerie-Album

Quote from: Ccecil on February 12, 2006, 05:56:13 PM
Correct 3 mistakes. Ver 1.15 http://www.h2.cz/czech.zip
Czech language file czech.php (iso-8859-2) ver. 1.15
for Coppermine 1.4.2

Nakis

Quote from: GauGau on March 02, 2006, 06:45:50 PMThose are special fields that appear only when enabled in coppermine's config - you should translate them.
I didn'd find these in the language file (and I searched for them).

Quote from: GauGau on March 02, 2006, 06:45:50 PMcharsetmgr.php
Since the language file I use is UTF-8 everything is fine to the script and it prompts me to leave the page.
You can have a look at the pic and see what I mean...

Nakis

Joachim Müller

Quote from: Nakis on March 02, 2006, 11:48:36 PM
I didn'd find these in the language file (and I searched for them).
Well, why don't you translate it anyway, it won't hurt. If you refuse, it doesn't matter either.

Quote from: Nakis on March 02, 2006, 11:48:36 PMSince the language file I use is UTF-8 everything is fine to the script and it prompts me to leave the page.
You can have a look at the pic and see what I mean...
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.

Joachim Müller

Quote from: Ccecil on March 02, 2006, 08:33:40 PM
new czech.php version 1.20
Your version is outdated, please use the CVS checkout for modifications. Merging your changes with the version in the CVS.

Nibbler

Quote from: Nakis on March 02, 2006, 03:27:58 PM
Fields of the user registration form:
Location
Interests
Website
Occupation
Biography

I didn't find these fields anywhere so they weren't translated.

That's fine, the names of the custom fields are stored in the database and cannot be translated. It is up to the end user to rename them as they see fit.

Makc666


Nakis

Quote from: GauGau on March 03, 2006, 07:00:28 AMWell, why don't you translate it anyway, it won't hurt. If you refuse, it doesn't matter either.
You covered me about this one with your 2nd post so, I will just leave it this way...

Quote from: GauGau on March 03, 2006, 07:00:28 AMThis 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).

The file is in UTF-8 format.

Nakis

Ccecil


Joachim Müller

@Ccecil: thanks for your continued contributions, but please use the most recent version from the cvs (http://cvs.sourceforge.net/viewcvs.py/coppermine/stable/lang/czech.php) for your updates, as I always have to convert your contributions before I can add them.

liorda

hebrew translation (only the frontend so far, and only non-utf).

i've started from 0, because i didn't know there is 1.3 version.

i'll continue working on it but it may take some time..

Giasher

Quote from: GauGau on November 11, 2005, 01:08:46 AM
Thanks for the contribution - however, the file is causing an error for me when uploading it to the coppermine demo and trying to run it using the georgian language file:. Could you please review it?
quoting from the "Re: [Help wanted]: Translations for CPG1.3.x"

Ooooops, sorry
here is how it looks like for 1.3.5 - http://www.gia.ge/mkportal/modules/coppermine/index.php

CPG 1.4.4 Georgian (UTF8) file is here - http://www.gia.ge/zzz/georgian.zip
Sorry again - would You be so kind to check it?