Spanish lang

[jmatute]

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,

[jmatute]

You might want to focus on [...] particular plugins.

Google Analytics Plugin is mine!

Regards,

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

Saludos,

[jmatute]

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


Regards.

[Joachim Müller]

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

[Josemic]

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

[Joachim Müller]

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.

[Josemic]

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.

[Joachim Müller]

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

You haven't done as suggested per board rules 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

[Josemic]

You haven't done as suggested per board rules 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.

[Joachim Müller]

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.

[jmatute]

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,

[Αndré]

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.

[jmatute]

Last version.

Regards,
José Luis.

[Αndré]

Last version.

Committed in r7504.

[jmatute]

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,

[Αndré]

Committed in r7505.

[jmatute]

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 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.htm	OK	OK	Needs translation	6
administration.htm	OK	OK	OK	5
admin-tools.htm	OK	OK	Needs translation	5
albums.htm	OK	OK	Needs translation	6
auto-installers.htm	OK	OK	Needs translation	4
banning.htm	OK	OK	Needs translation	5
bbcode.htm	OK	OK	Needs translation	5
bridging.htm	OK	Needs translation	Needs translation	4
categories.htm	OK	OK	Needs translation	6
comments.htm	OK	Needs translation	Needs translation	5
configuration.htm	OK	OK	Partial translation	9
copyrights.htm	OK	OK	OK	6
credits.htm	OK	OK	OK	2
dev.htm	OK	OK	Needs translation	4
dev_coding.htm	OK	OK	Needs translation	2
dev_config.htm	OK	Needs translation	Needs translation	1
dev_database.htm	OK	Needs translation	Needs translation	2
dev_documentation.htm	OK	Needs translation	Needs translation	2
dev_files.htm	OK	OK	Needs translation	2
dev_javascript.htm	OK	Needs translation	Needs translation	3
dev_plugin_api.htm	OK	Needs translation	Needs translation	3
dev_plugin_hooks.htm	OK	Needs translation	Needs translation	3
dev_plugins.htm	OK	Needs translation	Needs translation	3
dev_subversion.htm	OK	Needs translation	Needs translation	2
dev_superglobals.htm	OK	Needs translation	Needs translation	3
dev_tools.htm	OK	Needs translation	Needs translation	4
dev_update.htm	OK	Needs translation	Needs translation	1
dev_vars.htm	Needs completion	Needs translation	Needs translation	3
dev_versioncheck.htm	OK	Needs translation	Needs translation	1
empty.htm	OK	OK	OK	5
errors.htm	OK	OK	Needs translation	6
exif.htm	OK	OK	Needs translation	4
export.htm	OK	OK	Needs translation	3
faq.htm	OK	OK	Needs translation	5
files.htm	OK	OK	Needs translation	6
groups.htm	OK	OK	Needs translation	6
index.htm	OK	OK	Partial translation	8
install.htm	OK	OK	Needs translation	9
install_faq.htm	OK	OK	Needs translation	7
install_permissions.htm	OK	OK	Needs translation	7
install_screen.htm	OK	OK	Needs translation	6
keywords.htm	OK	OK	Needs translation	5
known_issues.htm	OK	OK	Needs translation	3
languages.htm	OK	OK	OK	5
performance.htm	OK	OK	Needs translation	3
php-content.htm	OK	OK	Needs translation	3
plugins.htm	OK	Needs translation	Needs translation	5
quickstart.htm	OK	OK	Needs translation	4
requirements.htm	OK	OK	Needs translation	6
script.js				8
start.htm	OK	OK	Needs translation	7
testing.htm	OK	OK	Needs translation	8
theme.htm	OK	OK	Needs translation	5
theme_copyright.htm	OK	OK	Needs translation	5
theme_create.htm	OK	OK	Needs translation	5
theme_create_matching_page_tutorial.htm	Needs completion	Needs translation	Needs translation	5
theme_examples.htm	OK	Needs translation	Needs translation	5
theme_graphics.htm	OK	OK	Needs translation	5
theme_style_css.htm	Needs completion	OK	Needs translation	5
theme_template.htm	OK	OK	Needs translation	5
theme_theme_php.htm	OK	OK	Needs translation	5
theme_upgrade_13x-14x.htm	OK	Needs translation	Needs translation	5
theme_upgrade_14x-15x.htm	Needs review	OK	Needs translation	5
theme_user-contributions.htm	OK	Needs translation	Needs translation	5
toc.htm	OK	Needs translation	Needs translation	5
translation.htm	OK	OK	Needs translation	8
uninstall.htm	OK	OK	OK	5
upgrading.htm	OK	OK	Needs translation	9
upload_troubleshooting.htm	OK	OK	Needs translation	9
uploading.htm	OK	OK	Needs translation	7
uploading_batch-add.htm	OK	OK	Needs translation	7
uploading_http.htm	OK	OK	Needs translation	7
uploading_xp-publisher.htm	OK	OK	Needs translation	7
users.htm	OK	OK	Needs translation	5
watermarking.htm	OK	OK	Needs translation	5

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

[jmatute]

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,

[Joachim Müller]

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

[jmatute]

Hi,

Please find attached several files translated to Spanish. You can see them in action here.

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,