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

[Makc666]

 
Heh. I finished Russian translation.
It is made from 1 line till last line all by myself.
I check very thoroughly for grammar erros and misspelling and etc. but I know, as it is not my first translation, that there are BUGs in this translation also.
So I will be very much appreciative for any comments from Russian users.

Some words in native language:
Êîðî÷å, ïåðåâîä ñóïåð. Äåëàëñÿ è âûëèçûâàëñÿ äîëãî è î÷åíü íóäíî. Âû áóäèòå â âîñòîðãå
Íàéäåòå íåòî÷íîñòè è îøèáêè, ïðèñûëàéòå, ïðîàíàëèçèðóåì.

[sbourdon]

French translation updated!

Only minor changes, where some words had not been translated ( and/or ).  Also, minor bug fixes ( \\ instead of \ ). 
Name of the original translator has not been changed, only the date.

[Joachim Müller]

Thanks for the contributions, they're both available in the CVS (use web cvs to get them).

@sbourdon: your fixes are only partly correct - you mustn't re-introduce bugs that have been ironed out in previous versions already: the 3 backslashes in a row, followed by a single quote are needed for escaping stuff that will go into JavaScript alert boxes, please do not commit untested translations.

Joachim

[Makc666]

Thanks.
Hope my translation will be avalible soon on the main site also.

Thanks for the contributions, they're both available in the CVS (use web cvs to get them).

@sbourdon: your fixes are only partly correct - you mustn't re-introduce bugs that have been ironed out in previous versions already: the 3 backslashes in a row, followed by a single quote are needed for escaping stuff that will go into JavaScript alert boxes, please do not commit untested translations.

Joachim

[mcjc]

I'm starting the translation for the Esperanto language for 1.3x version 

[Vadim]

Hi2all!

I have updated the Russian language file. I've corrected grammatical, factological errors and misprints.  which were in translation. I didn't change an author just the date. This file is tested in a gallery with over 6000 photos and over 400000 views.

I think it's a good replacement for an existing file, but you can also add it as a second version.
All who use Russian can take a look @ http://www.karjamaa.ee/album to test it.

I hope this file will be useful

[Joachim Müller]

what russian language file - the one that came with the coppermine package or the one contributed by Makc666  only recently? You have to understand that we can't tell if a translation is good or bad, wether it contains errors or not. Best thing would be if you (the translators who worked on a particular lanuage, in your case russian) could share your thoughts and come up with a "common" version that has both.

Joachim

[Tranz]

This seems like one of those times when using something like Wiki for collaboration might be very useful.

[CapriSkye]

here's an updated version for chinese-traditional language. only some minor changes to reflect on SMF's translation. thanks

[ZiN]

Slovak translations file for CPG1.3.2 is here 

[ZiN]

how to delete message ?

[Tranz]

Post deletion is not enabled here.

[Joachim Müller]

@ZiN: thanks for your contribution - see http://forum.coppermine-gallery.net/index.php?topic=4623.msg20005#msg20005 and http://coppermine.sourceforge.net/team/

Joachim

[chtito]

This is the corrected french translation php file.

• The date format are corrected.
• The spelling has been corrected
• Some missing translations were added

Cheers!

[Joachim Müller]

Thanks for your contribution, but your version is not based on the most recent french language file from the cvs - there already has been a submission/fix on 2004-09-28 that addressed some spelling errors. Your version differs in 31 lines from the one that exists in the repository. The translators have submitted french.php and french-utf-8.php, which differed, leading to a version gap between the two files. As I can't tell which version is "more correct", I have to rely on the french speaking community to fix those issues.

If you're ready to take over this task, please check out the most recent version of the two files from the web cvs or use the copies I attached to my posting. Then use a diff viewer (winmerge recommended) to find out about the differences between your version and the version in the cvs. Finally, provide one file (that has all fixes from all versions) with ISO-8859-1 encoding and let me convert it to utf-8.

Thank you

Joachim

[chtito]

You are right. The last cvs version had many excellent corrections. I merged both versions.

There is a little problem with encodings: french cannot be properly encoded in latin1 because of the letter "œ", which appears in three words in the translation. So I made a latin1 version (which, in my opinion, should be dropped in the future) and a utf-8 version, the only difference being that "œ" becomes "oe" in the latin1 version.

Cheers,

== Olivier

PS. I just used "diff"...

[Joachim Müller]

Olivier,

thanks for your contribution. I understand that not all chars can be represented using iso-8859-i and that utf-8 is the way to go for the future, that's also what all recomendations say (e.g. http://www.w3.org/International/O-charset-lang.html ), but currently there are issues with many editors that don't "understand" proper utf-8 encoding - that's why we currently have two versions of all language files.
Your files will go into the cvs, thanks again.

Joachim

P.S. Usage of "diff" is of course the best solution, and it shows you're an expert with a good operating system

[chtito]

I think that it would be a good idea to consider moving to a single encoding for coppermine (utf-8). Most people who use coppermine don't even know what an encoding is. They will just use whatever encoding is provided in coppermine. Currently, all the browser that i know of support utf-8 encoding (yes, even MSIE!). I therefore suggest the following steps:

• Make utf-8 as the default encoding for all new installations of coppermine. This could easily be done for the version 1.4.
• Code a php function that converts the content of the database from the current encoding into utf-8. That function would be used in the update.php file, when updating to the 1.4 or to the 1.5 version of coppermine.
  

The advantages of having a single encoding are innumerable. Only one single type of language file needs to be maintained. People can put symbols in their comments (like ★ or ♥). They are not stuck with one single language. Etc. etc. Shortcommings? I can't see any. But your reactions are welcome.

cheers,

== Olivier

[Joachim Müller]

Shortcommings? I can't see any. But your reactions are welcome.

I can see one: bad editors for M$ users - notepad.exe is not very usefull for handling utf-8 encoded files (although it basically can handle it). Would make creation of translations hard for non-experts.

Joachim

P.S. I just noticed there's the usual line-break issue with your language file contributions, could you please save them with br and lf, so they work both in Lunix and Windows world? Thanks

[chtito]

Yes but who needs to edit files encoded in ut-8? Everything is handled by the code. The translators can translate from english to their language in any encoding they want, and then we (at least I can do that) convert their file to utf-8.

For the user of coppermine it makes no difference what encoding is used. As i said, most users don't even know what encoding means. It is therefore unnecessary for them to choose an encoding and also a language file with a weird extension (utf-8 or not). They should just choose the language, and we take care of the rest.

The utf-8 support of coppermine is wonderful, but it is not advertised enough.

So, what about making utf-8 the default encoding for the new installs of coppermine?

cheers,

== Olivier