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