I have been translating parts of the file in English, to pass into Spanish. I have translated and the most important partsHave you used fermunoz' language file as base or have you started from scratch?
accidentally, I erased the line breaksI haven't committed your file yet because of that reason.
http://www.megaupload.com/?d=F9CAWFVEPlease attach your file to your forum post next time. I've done this in this post. See attachment.
accidentally, I erased the line breaks
$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);http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/docs/en/languages.htm#language_manager
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.
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.
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)
Hi,
Please find today's file attached.
See you tomorrow,
Please don't send emails around. Instead, attach what you have to this thread as suggested.Hi,
Edit changes went into rev 7481.Fixed typo in update.sql in r7483.
Hi,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.
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.
Hello,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.
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.
So, wich one is the good file????
I start translating tomorrow!!!
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,Maybe that helps: http://documentation.coppermine-gallery.net/en/dev_tools.htm#dev_tools_editor
So, wich one is the good file????Always use the file from the repository.
Hi,
Nearly there...
Regards.
You might want to focus on [...] particular plugins (http://forum.coppermine-gallery.net/index.php/board,97.0.html).
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 fileTechnically 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.
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.
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, 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
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
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.
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.
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.
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.
Last version.Committed in r7504.
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: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.
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
Cheers
Joachim
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.
you haven't based your translation on the file script.js from the svn repository, but the one based on your contribution from Wednesday.
The edit I had performed against script.js ... was too drastical to merge the changes back
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.
Please find attached some filesThanks for the update - changes went into rev 7541
3 new links to install.htm; zip renamed to script_en.zipHm, 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.
I don't know if someone had these ideas (related to translation) before:The file is already too big, consuming too many resources on older clients. Adding even more to it is not an option imo.
- 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 twiceNot 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).
Thanks for the update - changes went into rev 7541You'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.
Sorry! Don't know what happened. Here it is.
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!
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.
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.
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).
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.