[Help wanted]: Translations for CPG1.3.x - Page 9 [Help wanted]: Translations for CPG1.3.x - Page 9
 

News:

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

Main Menu

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

Started by Joachim Müller, March 16, 2004, 07:10:56 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

bryandel

Gaugau, I've finished translating Filipino/Tagalog. What should I do next?

Joachim Müller

Quote from: marcos on December 26, 2004, 01:15:58 PM
Could someone give me the 1.4.0 to translate it ?
Português / BraSil
Starting a cpg1.4 translation doesn't make sense at this stage of development yet - we haven't agreed on a feature freeze. Once there is a feature freeze, we will inform the translators and post publicly, in a thread similar to this one. Please note that this thread is dedicated to cpg1.3.x translations. You will find out more about cpg1.4 if you go to the cpg1.4 bugs/testing board and read the sticky thread Important (must read!): "cpg1.4 testing/bugs board" rules and regs.

Quote from: bryandel on December 26, 2004, 01:19:13 PM
Gaugau, I've finished translating Filipino/Tagalog. What should I do next?
Please zip the translation and attach it to your next posting here (using the "Additional options" link at the bottom of the page when composing a message).

Thanks

Joachim

marcos

Thanx GauGau,

l'll wait to translate the 1.4 ...
goingtowritethislaterbecausemyspacebarisnotworkingproperly

Hein Traag

Seeing that there is already a dutch translator i assume that is covered enough. Should it be needed to translate to dutch i can always help if needed should the other one not be avaible.

shaneholden

I want to create a translation for the Irish language (Gaeilge)

How do I go about doing this?

I am not a master of php.....

shaneholden

please contact me via email........

shaneholden@gmail.com

Joachim Müller

Refer to Documentation: Translating Coppermine into other languages, Translator's guide, First post on this thread.
Please understand that we can not maintain any others methods of communication (like email), but postings on this forum.

Joachim

owen

Attached is the translation into Cymraeg (Welsh). Also included in the zip and tar.gz files is the Ddraig Goch (Welsh Flag). I do not know what to do regarding utf-8 or whatever it is called. Please let me know if I have forgotten to do something.

Diolch yn fawr,    Owen

Joachim Müller

Very good work - providing the flag is a very good idea as well. Don't worry about the utf-8 version, we'll take care of this and create it accordingly. There are some minor errors though: in lines that have the comment //js-alert next to them, you have to be particularly mindfull of the escape strings: those lines will end up in JavaScript Message boxes, so you have to escape single quotes not only once (like this "Peter\'s pics"), but actually three times (like this "Peter\\\'s pics"). Anyway, I went through your translation and modified it accordingly (see attachment). I'll add it to the download section, cvs and demo asap.
Thanks for your contribution.

Joachim

chtito

@Gaugau: I think that your editor converted all the diacritics in html code... ;)

@owen: Please consider translating the dates as well. Moreover:
Quote from: chtito on December 15, 2004, 12:21:41 AM
%I and %p are rarely used except in the US and a few other English speaking countries. That may be a good tip for the other translators as well.
Thank you for the translation!

== Olivier
Vous pouvez poser vos questions en français sur le forum francophone !

owen

Quote from: GauGau on January 05, 2005, 04:49:20 PM
There are some minor errors though: in lines that have the comment //js-alert next to them, you have to be particularly mindfull of the escape strings: those lines will end up in JavaScript Message boxes, so you have to escape single quotes not only once (like this "Peter\'s pics"), but actually three times (like this "Peter\\\'s pics"). Anyway, I went through your translation and modified it accordingly (see attachment). I'll add it to the download section, cvs and demo asap.
Thanks for your contribution.

Joachim

Thanks very much for this - I had no idea!
(I don't understand much about php but do understand quite a lot about Welsh!)
Diolch - Owen

Joachim Müller

@owen: I modified the very first posting of this thread to contain the link both to the demo and the download to the welsh file.

@chtito: thanks for spotting, could you please fix the encoding crap I created (I committed to the stable branch) and then commit it to the devel branch of the cvs as well? Thanks in advance.

Joachim

chtito

@Gaugau: i'm affraid i can't fix your modification, because you translated all the diacritics in html markups... So i took the original translation and i don't understand where the mistakes are. Can you enlighten me?  ;D

== Olivier
Vous pouvez poser vos questions en français sur le forum francophone !

Joachim Müller

k, now I see. I'm sorry, I thought I had disabled the option in my editor to replace the chars with html equivalents - obviously I haven't. I just committed a fresh copy of welsh.php to the stable branch.
Here's what I did (and a hint to all future translators): all strings in the language file that will later end up in the output as JavaScript alerts are being tagged with js-alert in the language file - they need to be treated differently than the rest of the translation when it comes to the use of single quotes: instead of only one backslash ("\") that is used to escape the single quote (e.g.
Quote'access_denied' => 'You don\'t have permission to access this page.',
), you have to insert thre backslashes ("\\\") before each single quote, because one of them is used to escape the php single quote, one of them is needed to remain in the code to escape it in the JavaScript output once again, and the third is needed to escape the second one. As an example:
Quote'confirm_delete' => 'Wyt t\'n siwr dy fod eisiau DILEU y categori hwn', //js-alert
in the original file welsh.php that is contained in Owen's contribution has to become
Quote'confirm_delete' => 'Wyt ti\\\'n siwr dy fod eisiau DILEU y categori hwn', //js-alert
. Not doing this will result in JavaScript errors (only visible in IE by default) and of course the JavaScript alerts will not fire up. This used to have a big impact in the past, for example in the french language file, where some translator didn't escape the single quotes in the albmgr.php section of the language file, so users of the french language file were unable to create albums.

Joachim

chtito

@Gaugau: thanks, i fixed it

@Owen: Please consider translating the dates as well!! Otherwise wlsh users will complain and ask why the dates are displayed in English... I re-requote myself:
%I and %p are rarely used except in the US and a few other English speaking countries. That may be a good tip for the other translators as well. Please translate all the date formats!

Have a look at http://www.php.net/manual/en/function.strftime.php to understand how the date formats work.
Vous pouvez poser vos questions en français sur le forum francophone !

Joachim Müller

Well, Wales is in the UK - I guess all Welsh people speak English as well, so maybe the language format isn't that wrong after all  ;)

Joachim

chtito

Yes, maybe you're right... ;D I'm pretty sure that the date formats are different though: %m/%d/%y is typically US. But since no brit has ever complained about the date format, let's keep it as it is for the welsh as well.

I'll add it as it is in the stable branch, then.
Vous pouvez poser vos questions en français sur le forum francophone !

Casper

ok, I'll be the first Brit to moan.  We do not use the US methods.

I just changed on my site before.  We use the formats as below;

Short date = 31.1.05

Long date = Mon 1st Jan 2005.

We always put the day before the month.

We can use either the 12 hour clock, or the 24, but when using the 12 hour clock we use single figures without a leading 0, i.e., 7.30am/7.30pm, not 07.30am/07.30pm. so when using the 24 we do not need or use the am/pm, just 07.30/19.30.

I can't speak for the Welsh language, but my mother-in-law, who is 100% Welsh (but cannot speak the language) uses the same date format as the rest of us brits.
It has been a long time now since I did my little bit here, and have done no coding or any other such stuff since. I'm back to being a noob here

donnoman

I'm cool with having a english_us, with an american flag.. Since the main version of english is a brit flag right now anyway, it might as well stay the international version.

I will say that using the english file as is, hasn't bothered me one iota. We're used to them Brits mispelling our words  ;D


Casper

For the info of non dev team readers, this is now being discussed on the dev board, and may be introduced in 1.4.


@ Donnoman,
I think a US version would be good, so we can add all the little pics so you yanks can see what we mean when big words are used they don't understand.  And they can keep the am/pm on the 24 hour clock, so they realise that anything after 12.00 is in the afternoon.
:P ;D ;)
It has been a long time now since I did my little bit here, and have done no coding or any other such stuff since. I'm back to being a noob here