forum.coppermine-gallery.net

Support => cpg1.5.x Support => cpg1.5 language => Topic started by: Fico on March 10, 2010, 06:03:46 pm

Title: Spanish lang
Post by: Fico on March 10, 2010, 06:03:46 pm
Is someone already working on the spanish version of the lang file for 1.5.3?

I'll be glad to translate it, but I don't want to rework something someone else is working on.
Title: Re: Spanish lang
Post by: Αndré on March 10, 2010, 07:30:03 pm
I'm not sure. Fabricio said several times that he will create the Spanish language file, but there's no contribution by now.
Title: Re: Spanish lang
Post by: fermunoz on March 28, 2010, 07:05:58 am
I began tonigth, but i am so tired.  I just did a few lines. Please work over this file and upload again. I think in 2 days we can finish. (excuse my english)
Title: Re: Spanish lang
Post by: Joachim Müller on March 28, 2010, 02:48:58 pm
Thanks a lot for your contribution; I'm glad that finally someone started working on the Spanish language file. I have added your work in progress to the subversion repository; please use that version (http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/lang/spanish.php?view=log) to continue, as I had to change some things around. Also please use an editor that is capable to handle utf-8 encoded files (I can recommend notepad++, see Tools recommended by the devs -> Text editors (http://documentation.coppermine-gallery.net/en/dev_tools.htm#dev_tools_editor) and Translation Guide -> Editors & Tools (http://documentation.coppermine-gallery.net/en/translation.htm#translation_editors))
Title: Re: Spanish lang
Post by: Joachim Müller on April 13, 2010, 08:19:38 am
Any news on the language file?
Title: Re: Spanish lang
Post by: dtc on April 24, 2010, 07:40:26 am
hello, I have been translating parts of the file in English, to pass into Spanish. I have translated and the most important parts, but there is a problem: They accidentally, I erased the line breaks, so there remains only that someone gave you the space and corresponding jumps. I leave here in case anyone wants to do, it's almost to Nadama enter the lines which correspond to pass to the next paragraph, though of course if they just translated, then I welcome that, at last, and very little missing.

Regards

///////Original en español

hola, he estado traduciendo partes de el archivo en ingles, para pasarlo al español. He traducido ya las partes mas importantes, pero hay un problema: sin querer, se me borraron los saltos de linea, asi que solo quedaria que alguien le diera los espacios y saltos correspondientes. Lo dejo aqui por si alguien quiere hacerlo, es casi dar nadamas enter en las lineas que corresponan para pasarlas al siguiente parrafo; aunque claro, si quieren acabar de traducirlo, pues bienvenido sea, al fin, ya es muy poco lo que falta.

Saludos
Title: Re: Spanish lang
Post by: dtc on April 24, 2010, 07:42:51 am
here it is: / Aqui esta:

http://www.megaupload.com/?d=F9CAWFVE
Title: Re: Spanish lang
Post by: Αndré on April 24, 2010, 10:25:43 am
Thanks for your contribution.

I have been translating parts of the file in English, to pass into Spanish. I have translated and the most important parts
Have you used fermunoz' language file as base or have you started from scratch?


accidentally, I erased the line breaks
I haven't committed your file yet because of that reason.


http://www.megaupload.com/?d=F9CAWFVE
Please attach your file to your forum post next time. I've done this in this post. See attachment.
Title: Re: Spanish lang
Post by: Josemic on April 26, 2010, 02:07:22 pm
How do you install this language??

I copied the php file in LANG folder, and it says the file is incomplete, so it wont work.

What do i do wrong???
Title: Re: Spanish lang
Post by: Joachim Müller on April 26, 2010, 03:01:14 pm
http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/docs/en/languages.htm#language_manager
Title: Re: Spanish lang
Post by: Αndré on April 26, 2010, 03:23:08 pm
accidentally, I erased the line breaks

I've written a little scripts that (hopefully) inserts all needed line breaks:
Code: [Select]
$text = file_get_contents('spanish.php');
foreach(array('$', 'EOT;', 'if', '{', '}') as $value) {
    $text = str_replace($value, "\n".$value, $text);
}
file_put_contents('spanish_new.php', $text);

Currently the Spanish language file is a big clump (see attachment). Maybe someone wants to beautify the file and check if everything works as expected. Maybe somebody has a better idea how to restore that file.
Title: Re: Spanish lang
Post by: Josemic on April 26, 2010, 03:39:08 pm
http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/docs/en/languages.htm#language_manager

Thanks. I will try to cooperate with dtc to improve the Spanish translation.

Regards
Title: Re: Spanish lang
Post by: Joachim Müller on April 26, 2010, 05:47:36 pm
Hm, this has been harder than I expected: dtc's contribution is still a partial translation, but it's more complete by far than what we previously got from fermunoz. Sadly, dtc hasn't built his work on the language file contributed by fermunoz, but has started from scratch, which is imo a big waste of resources. Sadly, dtc has made some serious mistakes with the file, removing some line breaks here and adding other lin breaks there. I have spent the past two hours or so trying to extract a working language file from what dtc has submit. The changes that I had to perform (and there were quite a lot of them) went into rev 7473 in the subversion repository. All who want to contribute to the Spanish language file should build on that version in the SVN and not on the file attached to this thread! Get the most recent spanish language file from the subversion repository by clicking here (http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/lang/spanish.php).

@all (potential) translators: there is quite a lot of documentation available for cpg1.5.x, and a huge section that explains translation (http://documentation.coppermine-gallery.net/en/translation.htm) in detail. Please read that section thoroughly before you start translating, this will save you (and us) much grief.

Nonetheless I want to say "thank you" again. Don't get me wrong in this aspect: we appreciate your contributions. It would be better though (much better) if they were in a manner that enables us to use your translation right away without the need to perform heavy edits.


@dtc: please don't translate variable names or array keys: the line $lang_translation_info['lang_name_español'] = 'español' (MX)'; in the file you provided is of course nonsense and needs to be $lang_translation_info['lang_name_english'] = 'Spanish';. Please be extra carefull with single quotes as content of strings.

Joachim
Title: Re: Spanish lang
Post by: jmatute on April 27, 2010, 05:12:12 pm
Hm, this has been harder than I expected: dtc's contribution is still a partial translation, but it's more complete by far than what we previously got from fermunoz. Sadly, dtc hasn't built his work on the language file contributed by fermunoz, but has started from scratch, which is imo a big waste of resources. Sadly, dtc has made some serious mistakes with the file, removing some line breaks here and adding other lin breaks there. I have spent the past two hours or so trying to extract a working language file from what dtc has submit. The changes that I had to perform (and there were quite a lot of them) went into rev 7473 in the subversion repository. All who want to contribute to the Spanish language file should build on that version in the SVN and not on the file attached to this thread! Get the most recent spanish language file from the subversion repository by clicking here (http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/lang/spanish.php).

@all (potential) translators: there is quite a lot of documentation available for cpg1.5.x, and a huge section that explains translation (http://documentation.coppermine-gallery.net/en/translation.htm) in detail. Please read that section thoroughly before you start translating, this will save you (and us) much grief.

Nonetheless I want to say "thank you" again. Don't get me wrong in this aspect: we appreciate your contributions. It would be better though (much better) if they were in a manner that enables us to use your translation right away without the need to perform heavy edits.


@dtc: please don't translate variable names or array keys: the line $lang_translation_info['lang_name_español'] = 'español' (MX)'; in the file you provided is of course nonsense and needs to be $lang_translation_info['lang_name_english'] = 'Spanish';. Please be extra carefull with single quotes as content of strings.

Joachim

Hi,

Please find attached a not-yet-finished spanish_es.php file. It's based on the 7476 rev in the subversion repository and using all I could reuse from fantastic Grumpywolf translation, but I coudn't finish it today - and I won't work on it again until tomorrow. Just my two cents in case someone keeps it going this afternoon.

I've created the localized version for Spain, since it seemed to me that the mexican version wouldn't be very clear for us here in Spain.

Sorry to say that I haven't used a CVS tool to integrate it in the repository - and I believe I coudn't use it anyway since I'm not a registered developer.
Title: Re: Spanish lang
Post by: Josemic on April 27, 2010, 05:39:08 pm
Hi,

Please find attached a not-yet-finished spanish_es.php file. It's based on the 7476 rev in the subversion repository and using all I could reuse from fantastic Grumpywolf translation, but I coudn't finish it today - and I won't work on it again until tomorrow. Just my two cents in case someone keeps it going this afternoon.

I've created the localized version for Spain, since it seemed to me that the mexican version wouldn't be very clear for us here in Spain.

Sorry to say that I haven't used a CVS tool to integrate it in the repository - and I believe I coudn't use it anyway since I'm not a registered developer.

If you need some help to finish it, just tell me what i have to do, and i will help you. :) (I am not a developer, but i can translate)
Title: Re: Spanish lang
Post by: Phill Luckhurst on April 27, 2010, 05:59:06 pm
Feel free to give it a go but always make sure you download the latest file from the repositry before you start. Whenever you stop work for any period of time make sure you  zip and save your file to the forum here so we can update the repositry. Then again, before you start download the latest version just incase anyone has made any changes.

You can always download the lates file from the repositry here - http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/lang/spanish.php

Please make sure you read the docs Joahim linked to above before you start.
Title: Re: Spanish lang
Post by: Αndré on April 27, 2010, 07:14:30 pm
Wait a second. If the Spanish language differs so much from the Mexican language, we have to create two different files imo. The current spanish.php in the svn repository is not the file jmatute attached, but dtc's one.

I suggest to stop collaborative work until we decided if we create two different language files or if we use only the language file translated from people from Spain.
Title: Re: Spanish lang
Post by: Phill Luckhurst on April 27, 2010, 07:24:24 pm
Good point though most Mexicans do understand spanish fully (at least from my understanding). It is a bit like the various regions of the German speaking world with slight differences but basically the same, or comparing British English to the odd version Americans have adopted (insert fishing emoticon). As we have a British and an American language file yes we could have both. My only concern is that it has already been very hard to get this translation done in the first place and as it is at least we have something all the Spanish speakers can live with.
Title: Re: Spanish lang
Post by: jmatute on April 28, 2010, 04:07:58 pm
Wait a second. If the Spanish language differs so much from the Mexican language, we have to create two different files imo. The current spanish.php in the svn repository is not the file jmatute attached, but dtc's one.

I suggest to stop collaborative work until we decided if we create two different language files or if we use only the language file translated from people from Spain.

Hi,

Sincerely: I woudn't use dtc's file in my gallery (and began my own translating on my own) not just due to the small mexican/spanish language differences, but because of errors in the translation. Accents are missing, gramatical errors, plain translation in several phrases, and so on. And I'm wondering why he didn't use 1.4.x translation as a base. IMHO it's wonderful - and I'm not connected to the translators in any way.

Not trying to upset anybody, but explaining my point of view.

And just another point: I'm not a 'character sets' expert. Everytime I've played with UTF-8 I messed my file (or so I thought), so I decided to keep working in ASCII. Could anybody convert it before uploading to the repository? Is this the reason why my gallery (http://www.carmenyjoseluis.com/galeria) messes up? (kind of a nonsense question)

Regards,
José Luis.
Title: Re: Spanish lang
Post by: jmatute on April 28, 2010, 04:29:27 pm
If you need some help to finish it, just tell me what i have to do, and i will help you. :) (I am not a developer, but i can translate)

Sent an email to your profile's email address.

Saludos/Regards
Title: Re: Spanish lang
Post by: jmatute on April 28, 2010, 04:50:49 pm
Hi,

Please find today's file attached.

See you tomorrow,
Title: Re: Spanish lang
Post by: jmatute on April 28, 2010, 04:53:30 pm
Hi,

Please find today's file attached.

See you tomorrow,

Sorry to say I'm not sure I attached last version. Just in case... this is it.
Title: Re: Spanish lang
Post by: Phill Luckhurst on April 28, 2010, 07:38:39 pm
I too noticed a lot of missing accents and other mistakes. I do not speak spanish but had lessons at school so remember enough to pick up on a few things. It is a real shame Fabriccio is quiet these days.

I'm mot trying to put down anyones work here by the way, it is great that you are all giving it a go. All language files are a great help. In the case of Spanish, there has alway been a large user base which is why I am surprised this has not been completed sooner. Keep up the good work all.
Title: Re: Spanish lang
Post by: Joachim Müller on April 28, 2010, 09:25:27 pm
Please don't send emails around. Instead, attach what you have to this thread as suggested.
I will create a separate Mexican language file. We have decided on the US English language file to be the standard file during development, that's why it is named english.php and not english_us.php. A similar thing can be said about Spanish: the file spanish.php should be the Spanish spoken on the Spanish mainland (Castellano). There can be other language files for the other versions of Spanish spoken throughout the world.
Edit changes went into rev 7481.

Joachim
Title: Re: Spanish lang
Post by: jmatute on April 28, 2010, 09:54:31 pm
Please don't send emails around. Instead, attach what you have to this thread as suggested.
Hi,

Just a quick note to attach it. I don't have time right now to translate it: my daughter will call me in less than a minute to tell her a bedtime story - hope you'll understand.


Hola,

Esta es la respuesta a tu oferta de ayuda. Ante todo, gracias. Vamos a ver cómo lo podemos terminar lo más pronto posible.

Para empezar descarga la última versión que esté en el foro. En él verás secciones que empiezan como '// File'. Para trabajar en el fichero de forma conjunta creo que lo mejor es que nos ocupemos cada uno de nosotros de los mensajes de un fichero. He puesto la palabra 'Traducida' en las que ya he terminado. Te recomiendo que elijas un fichero / sección que te resulte conocido, y que abras una vieja versión de la galería en español para copiar y pegar todo lo que puedas - la traducción de versiones anteriores es estupenda desde mi punto de vista.

Ya que dices que no eres programador: ten cuidado con las cosas que no hay que traducir (como los símbolos %s por ejemplo), y con las que hay que quitar: el apóstrofe que nosotros no usamos se tiene que poner como \' en el fichero de lenguaje inglés, como otro ejemplo. Ante la duda no lo toques, y deja una pmarca como '//  pendiente'. La doble barra es importante para que se sepa que es un comentario.

Cuando termines súbelo al foro - con un poco de suerte lo usarán para meterlo en el repositorio de versiones, y lo usaré yo mañana.

Si tienes dudas no tienes más que preguntar. No te puedo prometer respuesta hasta esta noche.
Title: Re: Spanish lang
Post by: Αndré on April 29, 2010, 08:11:27 am
Edit changes went into rev 7481.
Fixed typo in update.sql in r7483.
Title: File as of May the 1st
Post by: jmatute on May 01, 2010, 12:57:11 pm
Hi,

Just a quick note to leave it here.

Regards,
Title: Re: Spanish lang
Post by: Josemic on May 01, 2010, 01:05:38 pm
Tomorrow i will try to translate a big part. regards
Title: Re: File as of May the 1st
Post by: Αndré on May 01, 2010, 01:28:52 pm
Hi,

Just a quick note to leave it here.

Regards,
Your package contains 2 files: spanish.php and spanish_es.php. Please explain the difference and note that there exists only the language files spanish.php and spanish_mx.php in the repository.
Title: Re: File as of May the 1st
Post by: jmatute on May 01, 2010, 10:08:35 pm
Your package contains 2 files: spanish.php and spanish_es.php. Please explain the difference and note that there exists only the language files spanish.php and spanish_mx.php in the repository.

Hello,

It's just  a mistake when creating the zip file - the correct file is the spanish.php file. I'm attaching the fine one just in case.

Thank you.
Title: Re: File as of May the 1st
Post by: Αndré on May 01, 2010, 10:24:47 pm
Hello,

It's just  a mistake when creating the zip file - the correct file is the spanish.php file. I'm attaching the fine one just in case.

Thank you.
Updated Spanish language file in r7488. I noticed that your file was encoded in ANSI. Please use an editor that supports UTF-8 in the future. Thank you.
Title: Re: Spanish lang
Post by: Josemic on May 02, 2010, 01:26:21 am
So, wich one is the good file????

I start translating tomorrow!!!
Title: Re: Spanish lang
Post by: jmatute on May 02, 2010, 08:28:13 am
So, wich one is the good file????

I start translating tomorrow!!!

Hi,

Either the last one I uploaded yesterday or the one André updated in the repository (r7488).

I'll finish modifyalb.php section this morning - go ahead whith any other one(s) so we don't work twice.

Regards,
-----------------------
Hola,

El que colgué el último o el que André puso en el repositorio.

Yo terminaré la sección de modifyalb.php esta mañana. Coge otra(s) para no repetir trabajo.

Saludos,
Title: Re: File as of May the 1st
Post by: jmatute on May 02, 2010, 08:35:01 am
I noticed that your file was encoded in ANSI. Please use an editor that supports UTF-8 in the future. Thank you.

I'll try to, but here at home it's not so easy. Thank you,

Title: Re: File as of May the 1st
Post by: Αndré on May 02, 2010, 08:55:37 am
I'll try to, but here at home it's not so easy. Thank you,
Maybe that helps: http://documentation.coppermine-gallery.net/en/dev_tools.htm#dev_tools_editor
Title: Re: Spanish lang
Post by: Joachim Müller on May 02, 2010, 02:25:34 pm
So, wich one is the good file????
Always use the file from the repository.
Title: Re: Spanish lang
Post by: jmatute on May 03, 2010, 04:58:21 pm
Hi,

Nearly there...

Regards.
Title: Re: Spanish lang
Post by: Joachim Müller on May 03, 2010, 07:42:04 pm
Thanks again for your contribution. Went into rev 7496
Title: Re: Spanish lang
Post by: Josemic on May 03, 2010, 10:43:47 pm
Hi,

Nearly there...

Regards.

Good Job Jmatute!!

As you said, is nearly there!!

I am sorry I didnt find the time to Translate, but i can helpyou tonight. Tellme wich part can i translate, and you can focus in the rest, so we will finish it.
Title: Re: Spanish lang
Post by: Joachim Müller on May 03, 2010, 11:12:54 pm
You might want to focus on translating the docs (http://documentation.coppermine-gallery.net/en/translation.htm#translation_documentation) or particular plugins (http://forum.coppermine-gallery.net/index.php/board,97.0.html).
Title: Re: Spanish lang
Post by: jmatute on May 04, 2010, 12:16:22 am
Hi,

This is it.

Of course, there are some points to bear in mind about some specific sections:
- I haven't installed Coppermine from scratch yet (nor the old versions - someone did it for me). I'll try in next days so I can see if messages are the most appropiate ones.
- Nearly the same applies to upgrading a gallery, because I did it using the english language.
- Same applies to plugins, bridges, and some other sections
- And I'm sure there will be some other issues I'll change, or someone will point us to change. So you can expect new versions of this file.

¿Curious about how it looks like in spanish? Try http://www.carmenyjoseluis.com/galeria/

Regards,
Title: Re: Spanish lang
Post by: jmatute on May 04, 2010, 12:19:05 am
You might want to focus on [...] particular plugins (http://forum.coppermine-gallery.net/index.php/board,97.0.html).

Google Analytics Plugin is mine!

Regards,

--------------------
Me pido el Plugin Google Analytics!

Saludos,
Title: Re: Spanish lang
Post by: jmatute on May 04, 2010, 06:57:08 am
Hi,

Playing around I've found some issues. Those about language are corrected in this new file, and there are another two I can't work out on my own.

- In the main menu there are two options that I can't find in the language file: 'Files' and 'Information'
- Default names for the user-defined fields could/should be in the language file

You can see the attached image, or the one I uploaded here (http://www.carmenyjoseluis.com/galeria/displayimage.php?pid=121)


Regards.
Title: Re: Spanish lang
Post by: Joachim Müller on May 04, 2010, 07:40:50 am
This is it.
Thanks for your contribution. I applied a minor fix. Changes went into rev 7497/7498.

- In the main menu there are two options that I can't find in the language file: 'Files' and 'Information'
For the term "files" in this instance, the variable $lang_cat_list['pictures'] is being used. For the term "information", the variable $lang_common['information'] is being used. Your translations are $lang_cat_list['pictures'] = 'Fotos'; and $lang_common['information'] = 'Información'; // cpg1.5. You have translated the English term "file" with "foto". That's not a good idea, as Coppermine is a multimedia gallery and not only a photo gallery (I confess that the abbreviation "CPG" is a bit misleading in this aspect). You may be using it for photos only, but others won't. I suggest reviewing your translation accordingly. When the term "file" is being used throughout the language file, you should use the Spanish term "archivo" in my opinion. We went through this change already back in cpg1.3.x when multimedia capabilities were added and Coppermine turned from a image-only app to a multimedia app. The term "foto" may not be applicable anyway, as some may use Coppermine for images that are not photos (e.g. render files or other visual content that was not generated using a camera).

- Default names for the user-defined fields could/should be in the language file
Technically not possible right now. That would in fact be a feature request, which can not be taken into account at this stage, sorry. In fact, the default name for the stuff that resides the database is English, like "User gallery" etc.

Google Analytics Plugin is mine!
Please post in the corresponding announcement thread for the plugin you refer to.

Thanks again

Joachim
Title: Re: Spanish lang
Post by: Josemic on May 04, 2010, 09:37:45 am
Congratulations for your great job JMatute.

But, when i upload the spanish archive to "Lang" Folder, and I select spanish from the menu, the next error appears:


Parse error: syntax error, unexpected T_VARIABLE in /homepages/24/d320267612/htdocs/inmueble/lang/spanish.php on line 2299
Title: Re: Spanish lang
Post by: Joachim Müller on May 04, 2010, 09:43:04 am
That's why I already told you to use the subversion repository checkout instead of the attachment:
Always use the file from the repository.
Language file in the subversion repository doesn't cause the effect you describe for me. This is not a support thread anyway.
Title: Re: Spanish lang
Post by: Josemic on May 04, 2010, 10:00:35 am
That's why I already told you to use the subversion repository checkout instead of the attachment:Language file in the subversion repository doesn't cause the effect you describe for me. This is not a support thread anyway.

I am so sorry. I did not unverderstand you, and i know this is not a support thread, but I dont know where i can find the Spanish file to download instead of the attachment...

Where is the repository, i cant find it...

I am so sorry, but i need the file so badly.

Title: Re: Spanish lang
Post by: Joachim Müller on May 04, 2010, 10:08:03 am
I am so sorry, but i need the file so badly.
You haven't done as suggested per board rules (http://forum.coppermine-gallery.net/index.php/topic,54781.msg286951.html#msg286951) in any of your 10 postings so far >:(. Do so now, especially if you need support badly where no support is given!

Where is the repository, i cant find it...
http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/lang/spanish.php?view=log
Title: Re: Spanish lang
Post by: Josemic on May 04, 2010, 12:19:45 pm
You haven't done as suggested per board rules (http://forum.coppermine-gallery.net/index.php/topic,54781.msg286951.html#msg286951) in any of your 10 postings so far >:(. Do so now, especially if you need support badly where no support is given!
http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/lang/spanish.php?view=log

I didnt want "support". I wanted to help.

But it is okay. It wont happen again.

My excuses.
Title: Re: Spanish lang
Post by: Joachim Müller on May 04, 2010, 07:02:17 pm
All I asked for was a link to your gallery. Instead, you post excuses. That doesn't help. Just pasting the URL of your gallery into your posting and hitting the "post"-button should take less than 20 seconds and everybody would be happy again. So far, we haven't seen any help from you, but only questions. Become a giver instead of taker - that's what jmatute did, and we appreciate that very much.
Title: Re: Spanish lang
Post by: jmatute on May 05, 2010, 10:33:53 am
Hi,

Thanks for your contribution. I applied a minor fix. Changes went into rev 7497/7498.
For the term "files" in this instance, the variable $lang_cat_list['pictures'] is being used. For the term "information", the variable $lang_common['information'] is being used. Your translations are $lang_cat_list['pictures'] = 'Fotos'; and $lang_common['information'] = 'Información'; // cpg1.5.

I can't be sure right now (at work), but it seems these variables aren't being read. Will try to make sure this afternoon.

You have translated the English term "file" with "foto". That's not a good idea, as Coppermine is a multimedia gallery and not only a photo gallery (I confess that the abbreviation "CPG" is a bit misleading in this aspect). You may be using it for photos only, but others won't. I suggest reviewing your translation accordingly. When the term "file" is being used throughout the language file, you should use the Spanish term "archivo" in my opinion.

You're right - my translation was biased. I worked yesterday on it, but forgot the file here at work. I'll try to upload it today. And I've done some other changes - some pending variables translated and some other modified, both for accuracy and word/phrase length reasons. I haven't finished yet, although. Do you know when 1.5.4 will be released (aprox) so I'll do my best?

Technically not possible right now. That would in fact be a feature request, which can not be taken into account at this stage, sorry. In fact, the default name for the stuff that resides the database is English, like "User gallery" etc.

Such a pity. I truly believe they should be translated (can this be considered a feature request?  ;) ), and I've seen some similar stuff during some installations I made yesterday, from scratch. I'll post them in the install support board.

Regards,
Title: Re: Spanish lang
Post by: Αndré on May 05, 2010, 11:04:24 am
Do you know when 1.5.4 will be released (aprox) so I'll do my best?
No. But the languages files can be updated with every release.
Title: Re: Spanish lang
Post by: jmatute on May 06, 2010, 09:35:13 am
Last version.

Regards,
José Luis.
Title: Re: Spanish lang
Post by: Αndré on May 06, 2010, 10:12:12 am
Last version.
Committed in r7504.
Title: Re: Spanish lang
Post by: jmatute on May 07, 2010, 06:20:19 am
Hi,

Sorry to say there were some errors in last file (sent from work, hadn't tried it) and it didn't work. I did my first inmersion in PHP error-hunting and solved them.

Regards,
Title: Re: Spanish lang
Post by: Αndré on May 07, 2010, 08:05:33 am
Committed in r7505.
Title: Re: Spanish lang
Post by: jmatute on May 11, 2010, 11:51:57 am
Hi,

Please find attached the last version of the language file and the first one of the documentation (script.js file).

I've tried script.js here at work, but can't say the same about spanish.php - I can't upload it in my site from here.

I began translating script.js because I saw it's the TOC in all documents I entered - except for TOC.htm. After some days I found this post - if there isn't any update I'll keep this order. BTW, don't know if this thread is the appropiate one to post these files or I should upload them in the original one (http://forum.coppermine-gallery.net/index.php/topic,62976.msg312749.html#msg312749) where Joachim posted the matrix.

Regards,

Hello all,

the documentation in English is pretty complete, but a vast part of the translations is missing, so it's time to start organizing translation and maintenance of the docs.

I have come up with a document matrix where alle current documents are in. The table itself should be pretty self-explanatory. Those who have edit permissions here in this thread, feel free to edit the table to update it. Those who want to volunteer for translation of a particular file: go ahead and reply here.

The French team members (especially Francois as far as I can see) have done an enormous job so far, translating a lot of the documents - good job guys! Maybe it's time to start with the Spanish translation (or any other language) - feel free to contribute here (but please don't respond by saying something like "I'd surely like to see the documentation in my language XYZ as well" - this thread should not be one that consists of requests, but of contributions. OK, enough talk, here's the list:

File English French German Priority
admin_menu.htmOKOKNeeds translation6
administration.htmOKOKOK5
admin-tools.htmOKOKNeeds translation5
albums.htmOKOKNeeds translation6
auto-installers.htmOKOKNeeds translation4
banning.htmOKOKNeeds translation5
bbcode.htmOKOKNeeds translation5
bridging.htmOKNeeds translationNeeds translation4
categories.htmOKOKNeeds translation6
comments.htmOKNeeds translationNeeds translation5
configuration.htmOKOKPartial translation9
copyrights.htmOKOKOK6
credits.htmOKOKOK2
dev.htmOKOKNeeds translation4
dev_coding.htmOKOKNeeds translation2
dev_config.htmOKNeeds translationNeeds translation1
dev_database.htmOKNeeds translationNeeds translation2
dev_documentation.htmOKNeeds translationNeeds translation2
dev_files.htmOKOKNeeds translation2
dev_javascript.htmOKNeeds translationNeeds translation3
dev_plugin_api.htmOKNeeds translationNeeds translation3
dev_plugin_hooks.htmOKNeeds translationNeeds translation3
dev_plugins.htmOKNeeds translationNeeds translation3
dev_subversion.htmOKNeeds translationNeeds translation2
dev_superglobals.htmOKNeeds translationNeeds translation3
dev_tools.htmOKNeeds translationNeeds translation4
dev_update.htmOKNeeds translationNeeds translation1
dev_vars.htmNeeds completionNeeds translationNeeds translation3
dev_versioncheck.htmOKNeeds translationNeeds translation1
empty.htmOKOKOK5
errors.htmOKOKNeeds translation6
exif.htmOKOKNeeds translation4
export.htmOKOKNeeds translation3
faq.htmOKOKNeeds translation5
files.htmOKOKNeeds translation6
groups.htmOKOKNeeds translation6
index.htmOKOKPartial translation8
install.htmOKOKNeeds translation9
install_faq.htmOKOKNeeds translation7
install_permissions.htmOKOKNeeds translation7
install_screen.htmOKOKNeeds translation6
keywords.htmOKOKNeeds translation5
known_issues.htmOKOKNeeds translation3
languages.htmOKOKOK5
performance.htmOKOKNeeds translation3
php-content.htmOKOKNeeds translation3
plugins.htmOKNeeds translationNeeds translation5
quickstart.htmOKOKNeeds translation4
requirements.htmOKOKNeeds translation6
script.js8
start.htmOKOKNeeds translation7
testing.htmOKOKNeeds translation8
theme.htmOKOKNeeds translation5
theme_copyright.htmOKOKNeeds translation5
theme_create.htmOKOKNeeds translation5
theme_create_matching_page_tutorial.htmNeeds completionNeeds translationNeeds translation5
theme_examples.htmOKNeeds translationNeeds translation5
theme_graphics.htmOKOKNeeds translation5
theme_style_css.htmNeeds completionOKNeeds translation5
theme_template.htmOKOKNeeds translation5
theme_theme_php.htmOKOKNeeds translation5
theme_upgrade_13x-14x.htmOKNeeds translationNeeds translation5
theme_upgrade_14x-15x.htmNeeds reviewOKNeeds translation5
theme_user-contributions.htmOKNeeds translationNeeds translation5
toc.htmOKNeeds translationNeeds translation5
translation.htmOKOKNeeds translation8
uninstall.htmOKOKOK5
upgrading.htmOKOKNeeds translation9
upload_troubleshooting.htmOKOKNeeds translation9
uploading.htmOKOKNeeds translation7
uploading_batch-add.htmOKOKNeeds translation7
uploading_http.htmOKOKNeeds translation7
uploading_xp-publisher.htmOKOKNeeds translation7
users.htmOKOKNeeds translation5
watermarking.htmOKOKNeeds translation5
The priority column should be an indicator what file to translate first. The higher the number in that column, the more "urgent" is the need to see that file translated imo.

Cheers

Joachim

Title: Re: Spanish lang
Post by: jmatute on May 11, 2010, 06:17:53 pm
I've tried script.js here at work, but can't say the same about spanish.php - I can't upload it in my site from here.

Uploaded, everything seems to be OK.

Regards,
Title: Re: Spanish lang
Post by: Joachim Müller on May 11, 2010, 07:15:21 pm
Great work - I have added a Spanish branch of the docs in the subversion repository (http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/docs/es/) and added the corresponding files - they will be in revision 7527
Title: Re: Spanish lang
Post by: jmatute on May 13, 2010, 11:34:16 pm
Hi,

Please find attached several files translated to Spanish. You can see them in action here (http://www.carmenyjoseluis.com/galeria/docs/es/index.htm).

Of course there will be new versions, since every time I read them I find some phrase that can be told some other way.

Regards,
Title: Re: Spanish lang
Post by: jmatute on May 14, 2010, 12:07:09 am
BTW:

I don't know if you're aware of the two different 'you' that spanish language has: 'usted' (very formal, somehow being abandoned, exceptional among computer users) and 'tu' (used to be informal but gaining acceptance if you show respect, rare in formal docs, almost always used in computer-related issues).

I'm assuming that the respectful-but-not-so-formal approach is fine for the documentation. Somehow using 'usted' makes this help files (like the ones from 1.4.x) cold and distant.

I hope it's OK. But I'm open to hear other opinions.

Regards,
Title: Re: Spanish lang
Post by: Joachim Müller on May 14, 2010, 07:08:12 am
Thanks again. Your changes went into rev 7534 except your edit of script.js that I had to drop: you haven't based your translation on the file script.js from the svn repository, but the one based on your contribution from Wednesday. You have to take into account that I have performed several edits to the files you contributed, which would be lost if I just replaced the files in the svn repository with your files. The edit I had performed against script.js before committing it to the subversion (http://documentation.coppermine-gallery.net/en/dev_subversion.htm) repository was too drastical to merge the changes back in using a diff viewer. Please re-apply your edits to the file scripts.js that can be found in the subversion repository and re-attach your changed file. Please do always check out the subversion repository before editing your files. Sorry for the added work.

Joachim
Title: Re: Spanish lang
Post by: jmatute on May 14, 2010, 10:04:10 am
you haven't based your translation on the file script.js from the svn repository, but the one based on your contribution from Wednesday.

You are right - it's the one I use locally and easier for me to work on.

The edit I had performed against script.js ... was too drastical to merge the changes back

I've downloaded it, and I can see your modified it much more than I did. I use tools that 'checkout for edit', locking the file, so this issue doesn't occurs in my job.

Please re-apply your edits to the file scripts.js that can be found in the subversion repository and re-attach your changed file.

Done - and some new ones.

Please do always check out the subversion repository before editing your files. Sorry for the added work.

So I will remember (or at least will try) - even for the documentation files at the very moment I begin working on them. And modifications weren't that big.

BTW: I've seen some anchor points in the documentation files that aren't linked to from this script but similar paragraps/sections have an entry in it (for instance, First run (http://http:carmenyjoseluis.com/galeria/docs/es/upgrading.htm#versioncheck_first_run) in the upgrading.htm file. Suppose it's all right, isn't it?. Or should I report them?


[Edit] Sorry I forgor the attach.
Title: Re: Spanish lang
Post by: Joachim Müller on May 15, 2010, 08:12:17 am
Thanks again for your contribution. Well done on re-editing scripts.js. I have added it to the repository, revision 7535.
Please go ahead and report missing anchors in a separate thread. You're welcome as well to come up with a fixed version of docs/en/script.js that contains the missing anchors if you want.
Title: Re: Spanish lang
Post by: jmatute on May 18, 2010, 11:36:17 pm
Hi,

Please find attached some files:

docs/en/script.js - based on rev. 7515 or so I believe: 3 new links to install.htm; zip renamed to script_en.zip
lang/spanish.zip - based on rev. 7527
docs/en/script.js - based on rev. 7535
docs/en/upgrading.htm - based on rev. 7495; not yet finished

I don't know if someone had these ideas (related to translation) before:
- Modify scritp.js so there's a language file properly defined, and a fallback method.
- Link / embed script.js to toc.htm so translators doesn't work twice

I'm focused on the translation, so I won't try anythig about them for several weeks (being optimistic; months, being realistic).

and last but nost least: is there any trick to know which are the differences between a file and the one I used as a base? Think about upgrading.htm, for instance: I can't compare the spanish version and the english one, since translation is a difference by itself, but knowing which paragraphs have been added/modified would be an advance.

Regards,
Title: Re: Spanish lang
Post by: Joachim Müller on May 19, 2010, 08:08:26 am
Please find attached some files
Thanks for the update - changes went into rev 7541

3 new links to install.htm; zip renamed to script_en.zip
Hm, I'm not really sure why you attach so many files and go through such a huge effort to explain the file structure. Take a look at the zip archive I have attached: it contains exactly the same files you have added, but only within one archive. Looking at the archive you can see the structure pretty easily.

However: the file script.zip is broken for me (file size is zero) - I wasn't able to extract it's contents. Please re-attach!

I don't know if someone had these ideas (related to translation) before:
- Modify scritp.js so there's a language file properly defined, and a fallback method.
The file is already too big, consuming too many resources on older clients. Adding even more to it is not an option imo.
- Link / embed script.js to toc.htm so translators doesn't work twice
Not an option: search engine spiders will not take JS into account. The toc.htm file is the save fallback if JavaScript is not available for whatever reason. You don't have to update it frequently, but only before the actual release, using the output generated in your browser. If you don't know what I mean, don't worry: I'll take care of that.

and last but nost least: is there any trick to know which are the differences between a file and the one I used as a base? Think about upgrading.htm, for instance: I can't compare the spanish version and the english one, since translation is a difference by itself, but knowing which paragraphs have been added/modified would be an advance.
Use a diff viewer like WinMerge (http://winmerge.org/) to figure out differences between files on your client. Use the diff viewer built-into the web svn to figure out differences between revisions (example link (http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/lang/english.php?r1=7193&r2=7421)). Alternatively, use the diff viewer built into your local svn app (assuming that you are using TortoiseSVN (http://tortoisesvn.tigris.org/) or a similar graphical client).
Title: Re: Spanish lang
Post by: jmatute on May 19, 2010, 09:50:42 am
Thanks for the update - changes went into rev 7541
You're welcome.

Hm, I'm not really sure why you attach so many files and go through such a huge effort to explain the file structure. Take a look at the zip archive I have attached: it contains exactly the same files you have added, but only within one archive. Looking at the archive you can see the structure pretty easily.
You're right - I agree that the file structure is much clearer, but it seems not so easy/fast for me to create it (specially here at work) if files are in several directories, using the tools I have.

Anyway, if this is an issue, tell me so and I'll manage.


However: the file script.zip is broken for me (file size is zero) - I wasn't able to extract it's contents. Please re-attach!
Sorry! Don't know what happened. Here it is.

The file is already too big, consuming too many resources on older clients. Adding even more to it is not an option imo.

About time to render, I can confirm: we use IE6 here (don't ask nor laugh, please), and it takes more than 30s to display.

Here at work we had a 1Mb HTML file (nearly all the code was a JS script) that created nested tables up to 8 levels deep on the fly and took nearly 1 min. to render. But after creating just the 1st level, and populating only the nested table rows and cells the user clicked on,  it takes less than 1sec. I'll try to figure out if that idea can help here.


The toc.htm file is the save fallback if JavaScript is not available for whatever reason. You don't have to update it frequently, but only before the actual release, using the output generated in your browser. If you don't know what I mean, don't worry: I'll take care of that.

That sounded easy. I'm attaching toc.htm too. Hope that was the idea.

Use a diff viewer like WinMerge (http://winmerge.org/) to figure out differences between files on your client. Use the diff viewer built-into the web svn to figure out differences between revisions (example link (http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/lang/english.php?r1=7193&r2=7421)). Alternatively, use the diff viewer built into your local svn app (assuming that you are using TortoiseSVN (http://tortoisesvn.tigris.org/) or a similar graphical client).

Hmmm... No, I don't use that tools. Here we use UltraEdit (has a quite good diff viewer plugin), and I've just installed notepad++ at home (used to work with an old Ultraedit version). I'll try to manage with the svn diff viewer.

Regards,
Title: Re: Spanish lang
Post by: Joachim Müller on May 19, 2010, 10:37:17 am
Thanks again - went into rev 7544
Title: Re: Spanish lang
Post by: jmatute on May 19, 2010, 11:50:48 pm
Hi,

Upgrading.htm is finished. During the translation script.js (for spanish) and spanish.php were also modified. I didn't work on toc.htm  - I'd rather not work several times on it.

Regards,
Title: Re: Spanish lang
Post by: Joachim Müller on May 20, 2010, 07:28:41 am
Well done again, thanks. Changes went into rev 7550.

I didn't work on toc.htm  - I'd rather not work several times on it.
That's perfectly OK. What I wanted to say above: you don't have to edit that file each time, but only before a release (i.e. once in a while) - that's fine. The file docs/en/toc.htm lags behind docs/en/script.js as well.
Title: Re: Spanish lang
Post by: jmatute on May 25, 2010, 07:10:46 am
Hi,

I began working on configuration.htm, and found some typos in the language file.

Regards,
Title: Re: Spanish lang
Post by: Joachim Müller on May 25, 2010, 08:17:18 am
Thanks, changes went into rev 7565