Jump to content
jacmaes

Spanish es-ES

Recommended Posts

Here's my first draft for the Spanish translation. Please note that:

  • It's fairly complete, but not quite ready for production. Spanish is not my mother tongue (I'm French), but I've been living in Spain for 10 years so it should be acceptable. Contributions and suggestions are welcome. I will post updates as necessary.
  • This is Spanish for Spain. Some parts of the translations might not be appropriate in South American countries for example. In particular, I've used the less formal, more direct version of "you": "tú" as opposed to "usted", which is much more common in Spain.
  • I love ProcessWire and I'm glad I can contribute to this awesome project.

UPDATES:

  1. December 10, 2013: Translation files updated for dev version 2.3.8 (see "spanish-spain-december2013.zip" below)
  2. March 4, 2014: I've created a Github repository that I plan to update whenever possible. All updates will be posted there from now on.
  3. June 16, 2014. Update to 2.4.4.

spanish-spain.zip

spanish-spain-december2013.zip

Edited by jacmaes
  • Like 4

Share this post


Link to post
Share on other sites
Su trabajo es excelente, gracias!

Tú trabajo, you mean ;)

Share this post


Link to post
Share on other sites

Hi. I'm native Spanish speaker (from Argentina) and I'd like contribute to Jacmaes's translations or make a new one for Latin America. I like the idea to have a "formal" translation for an admin. When I say "formal", I mean use "usted" instead "vos" or "tu", but I'd want to know what is the opinion Ryan about that. BTW, I would like to take this opportunity to thank to him this fantastic CMS. I've not done any site using PW yet, but I realize its potential, so I want to express my deep adminiration for his great work.

Going back to the translation subject, I would need some advices or tell me what I should do to make a new Spanish version. I've started translating what Jacmaes did into Control Panel of PW. Am I in a good path?

Thanks in advance.
Best regards
Fernando

  • Like 2

Share this post


Link to post
Share on other sites

Thanks Fernando for your contribution. A Latin American version is indeed sorely needed. I'll be more than happy to collaborate with you so we can have two (or more) rock-solid Spanish versions. As a matter of fact, I was planning on revising my original work for a new Web project in Spanish that I'll be starting in about a month, and enlist the help of a native speaker from Spain to double-check everything.

My translation is for an older version of PW, so I suppose there must new fields to be translated anyway. 

As regards to your question about how to get started with the translation, if I remember well, I did everything from the control panel. As it's not always easy to determine the context of the original text in English, I think it's best to move back and forth between a live site and the control panel to sort out the intended meaning, which I did not do fully enough in the first place. 

Jacques

  • Like 3

Share this post


Link to post
Share on other sites

I was this morgning translating the "blank" fields and i've got a doubt...

"Abandoned" fields are fields used by modules that i haven't installed them yet???

I mean, system proposes to delete them... but i am not sure if deleting is a good thing if they are going to appear again if I install new modules.

he he he

Hugs from Spain!!!

And thanks for the help!!!

Share this post


Link to post
Share on other sites

Hello SadlyMistaken and welcome to PW forum.

"Abandoned" fields are translated, but source code was changed (localization string need update) or missing modules.

Good way for external modules localization could be release separate language pack and do not include them to core language pack. (Every user have different modules installed so let them choose). I am doing it in Czech language pack.

And seems like i will do git repo for them soon....

Share this post


Link to post
Share on other sites

Thanks so much for dissipating my doubts!!!

And thanks too for the welcome!!

I was reading the post where people are talking about core and module translations and for the moment i don't know what to choose (one translation file per module plus core, or several translation files each for module)... it is a really difficult question to solve...

Again, thanks :D

Share this post


Link to post
Share on other sites

Thanks biojazzard. I've gone quickly over your changes and added some more recent translations for the stable release of 2.4.0.

I've created a Github repository that I plan to keep updating whenever possible: https://github.com/jacmaes/pw-spanish

  • Like 1

Share this post


Link to post
Share on other sites

I never used github... and now i can choose between 2 sources...

I feel this is weiiiiiiird....

I think I only must to choose which ZIP file to download.. musn't I ?

Anyway Thanks a lot for 2.4.0 version, boys

Me encanta poder entender donde estoy haciendo click en mi sitio web.

También, muchas gracias por separar los módulos del core básico.

:D Mooooooooooooola

De nuevo, millones de gracias.

Share this post


Link to post
Share on other sites

SadlyMistaken, I can talk to biojazzard if he'd like to keep collaborating on future updates, and how we'd do that, so that there are no two parallel translations. But for now, the most up-to-date version can be found on my Github repository. You don't need to know anything about Github by the way, just click the "Download zip" button on the right column.

Share this post


Link to post
Share on other sites

The last update was 20 files, this has 126 fully translated.
Updated Sept/2014: ProcessWire 2.4.15. --> 126 files --> 100% translated. 


Files translated: 


wire--core--admintheme-php.json
wire--core--field-php.json
wire--core--fieldgroups-php.json
wire--core--fields-php.json
wire--core--fieldselectorinfo-php.json
wire--core--fieldtype-php.json
wire--core--fieldtypemulti-php.json
wire--core--functions-php.json
wire--core--inputfield-php.json
wire--core--inputfieldwrapper-php.json
wire--core--interfaces-php.json
wire--core--languagefunctions-php.json
wire--core--modules-php.json
wire--core--pagefile-php.json
wire--core--pageimage-php.json
wire--core--pages-php.json
wire--core--password-php.json
wire--core--process-php.json
wire--core--sanitizer-php.json
wire--core--session-php.json
wire--core--sessioncsrf-php.json
wire--core--wire-php.json
wire--core--wirecache-php.json
wire--core--wirehttp-php.json
wire--core--wiretempdir-php.json
wire--core--wireupload-php.json
wire--modules--admintheme--adminthemedefault--adminthemedefault-module.json
wire--modules--admintheme--adminthemedefault--adminthemedefaulthelpers-php.json
wire--modules--admintheme--adminthemedefault--default-php.json
wire--modules--fieldtype--fieldtypecomments--commentfilterakismet-module.json
wire--modules--fieldtype--fieldtypecomments--commentform-php.json
wire--modules--fieldtype--fieldtypecomments--commentlist-php.json
wire--modules--fieldtype--fieldtypecomments--fieldtypecomments-module.json
wire--modules--fieldtype--fieldtypecomments--inputfieldcommentsadmin-module.json
wire--modules--fieldtype--fieldtypedatetime-module.json
wire--modules--fieldtype--fieldtypefile-module.json
wire--modules--fieldtype--fieldtypefloat-module.json
wire--modules--fieldtype--fieldtypemodule-module.json
wire--modules--fieldtype--fieldtypepage-module.json
wire--modules--fieldtype--fieldtypepagetable-module.json
wire--modules--fieldtype--fieldtyperepeater--fieldtyperepeater-module.json
wire--modules--fieldtype--fieldtyperepeater--inputfieldrepeater-module.json
wire--modules--fieldtype--fieldtypeselector-module.json
wire--modules--fieldtype--fieldtypetext-module.json
wire--modules--fieldtype--fieldtypetextarea-module.json
wire--modules--fieldtype--fieldtypeurl-module.json
wire--modules--inputfield--inputfieldasmselect--inputfieldasmselect-module.json
wire--modules--inputfield--inputfieldbutton-module.json
wire--modules--inputfield--inputfieldcheckbox-module.json
wire--modules--inputfield--inputfieldcheckboxes--inputfieldcheckboxes-module.json
wire--modules--inputfield--inputfieldckeditor--inputfieldckeditor-module.json
wire--modules--inputfield--inputfielddatetime--inputfielddatetime-module.json
wire--modules--inputfield--inputfieldemail-module.json
wire--modules--inputfield--inputfieldfieldset-module.json
wire--modules--inputfield--inputfieldfile--inputfieldfile-module.json
wire--modules--inputfield--inputfieldfloat-module.json
wire--modules--inputfield--inputfieldform-module.json
wire--modules--inputfield--inputfieldhidden-module.json
wire--modules--inputfield--inputfieldimage--inputfieldimage-module.json
wire--modules--inputfield--inputfieldinteger-module.json
wire--modules--inputfield--inputfieldmarkup-module.json
wire--modules--inputfield--inputfieldname-module.json
wire--modules--inputfield--inputfieldpage--inputfieldpage-module.json
wire--modules--inputfield--inputfieldpageautocomplete--inputfieldpageautocomplete-module.json
wire--modules--inputfield--inputfieldpagelistselect--inputfieldpagelistselect-module.json
wire--modules--inputfield--inputfieldpagelistselect--inputfieldpagelistselectmultiple-module.json
wire--modules--inputfield--inputfieldpagename--inputfieldpagename-module.json
wire--modules--inputfield--inputfieldpagetable--inputfieldpagetable-module.json
wire--modules--inputfield--inputfieldpagetable--inputfieldpagetableajax-php.json
wire--modules--inputfield--inputfieldpagetitle--inputfieldpagetitle-module.json
wire--modules--inputfield--inputfieldpassword-module.json
wire--modules--inputfield--inputfieldradios--inputfieldradios-module.json
wire--modules--inputfield--inputfieldselect-module.json
wire--modules--inputfield--inputfieldselectmultiple-module.json
wire--modules--inputfield--inputfieldselector--inputfieldselector-module.json
wire--modules--inputfield--inputfieldsubmit--inputfieldsubmit-module.json
wire--modules--inputfield--inputfieldtext-module.json
wire--modules--inputfield--inputfieldtextarea-module.json
wire--modules--inputfield--inputfieldurl-module.json
wire--modules--jquery--jquerywiretabs--jquerywiretabs-module.json
wire--modules--languagesupport--languageparser-php.json
wire--modules--languagesupport--languagesupport-module.json
wire--modules--languagesupport--languagesupportfields-module.json
wire--modules--languagesupport--languagesupportpagenames-module.json
wire--modules--languagesupport--languagetabs-module.json
wire--modules--languagesupport--processlanguage-module.json
wire--modules--languagesupport--processlanguagetranslator-module.json
wire--modules--markup--markuppagefields-module.json
wire--modules--markup--markuppagernav--markuppagernav-module.json
wire--modules--pagepaths-module.json
wire--modules--pagerender-module.json
wire--modules--process--processfield--processfield-module.json
wire--modules--process--processfield--processfieldexportimport-php.json
wire--modules--process--processforgotpassword-module.json
wire--modules--process--processhome-module.json
wire--modules--process--processlist-module.json
wire--modules--process--processlogin--processlogin-module.json
wire--modules--process--processmodule--processmodule-module.json
wire--modules--process--processmodule--processmoduleinstall-php.json
wire--modules--process--processpageadd--processpageadd-module.json
wire--modules--process--processpageclone-module.json
wire--modules--process--processpageedit--processpageedit-module.json
wire--modules--process--processpageeditimageselect--processpageeditimageselect-module.json
wire--modules--process--processpageeditlink--processpageeditlink-module.json
wire--modules--process--processpagelist--processpagelist-module.json
wire--modules--process--processpagelister--processpagelister-module.json
wire--modules--process--processpagesearch--processpagesearch-module.json
wire--modules--process--processpagesort-module.json
wire--modules--process--processpagetrash-module.json
wire--modules--process--processpagetype--processpagetype-module.json
wire--modules--process--processpageview-module.json
wire--modules--process--processpermission--processpermission-module.json
wire--modules--process--processprofile--processprofile-module.json
wire--modules--process--processrole--processrole-module.json
wire--modules--process--processtemplate--processtemplate-module.json
wire--modules--process--processtemplate--processtemplateexportimport-php.json
wire--modules--process--processuser--processuser-module.json
wire--modules--session--sessionhandlerdb--processsessiondb-module.json
wire--modules--session--sessionhandlerdb--sessionhandlerdb-module.json
wire--modules--session--sessionloginthrottle--sessionloginthrottle-module.json
wire--modules--system--systemupdater--systemupdater-module.json
wire--modules--textformatter--textformatterentities-module.json
wire--modules--textformatter--textformattermarkdownextra--markdown-php.json
wire--templates-admin--debug-inc.json
wire--templates-admin--default-php.json
wire--templates-admin--topnav-inc.json
126 archivos 260.539 bytes




https://github.com/LuisSantiago/Processwire-Spanish/tree/master/Processwire-master-Spanish%20(100%25%20Translated)

  • Like 1

Share this post


Link to post
Share on other sites

nice to see yet another fully translated language.

But these 6 files have no translatable phrases (at least for me?). So you can skip them.

wire--core--interfaces-php.json 
wire--core--languagefunctions-php.json
wire--core--wire-php.json
wire--modules--languagesupport--processlanguagetranslator-module.json
wire--modules--textformatter--textformattermarkdownextra--markdown-php.json 
wire--templates-admin--topnav-inc.json

these two files can be translated, but don't have to. See comment inside files:

wire--modules--admintheme--adminthemedefault--adminthemedefaulthelpers-php.json 
wire--modules--admintheme--adminthemedefault--default-php.json 

FOR TRANSLATORS: please translate the file /wire/templates-admin/default.php rather than this one

Share this post


Link to post
Share on other sites

nice to see yet another fully translated language.

But these 6 files have no translatable phrases (at least for me?). So you can skip them.

wire--core--interfaces-php.json 
wire--core--languagefunctions-php.json
wire--core--wire-php.json
wire--modules--languagesupport--processlanguagetranslator-module.json
wire--modules--textformatter--textformattermarkdownextra--markdown-php.json 
wire--templates-admin--topnav-inc.json
these two files can be translated, but don't have to. See comment inside files:
wire--modules--admintheme--adminthemedefault--adminthemedefaulthelpers-php.json 
wire--modules--admintheme--adminthemedefault--default-php.json 

FOR TRANSLATORS: please translate the file /wire/templates-admin/default.php rather than this one
 

Thank you! I had json files with 0 phrases. I updated the repository.

Share this post


Link to post
Share on other sites

Oh! more translated lines!

Thanks a lot!

:D

You're welcome. :)  I will translate modules too.

Share this post


Link to post
Share on other sites

Hello,

I have tried to install this language (spanish (es-ES) v.2) on PW2.5

Wenn I try to edit a file from "admin/setup/language-translator/add/". It shows a message:

File does not exist: /wire\modules\Inputfield\InputfieldPageName\InputfieldPageName.module (Translation file not needed? Textdomain: wire--modules--inputfield--inputfieldpagename--inputfieldpagename-module)

But the file /wire\modules\Inputfield\InputfieldPageName\InputfieldPageName.module exists.

I have opened the json file with the translations I have observed that the attribute "file" is:

"file": "wire\\modules\\Inputfield\\InputfieldPageName\\InputfieldPageName.module", (note the double // )

Wenn I use the translator manager to create a new translation file, the value of this parameter ist:

 "file": "wire\/modules\/Inputfield\/InputfieldPageName\/InputfieldPageName.module",

I have changed in all my language files the // by \/ and it works.

Can someone test if I'm wrong or this error are produced due to this wrong attribute in the translation files?

Thank you in advance.

Raul Garcia.

  • Like 1

Share this post


Link to post
Share on other sites

Hello,

I have tried to install this language (spanish (es-ES) v.2) on PW2.5

Wenn I try to edit a file from "admin/setup/language-translator/add/". It shows a message:

File does not exist: /wire\modules\Inputfield\InputfieldPageName\InputfieldPageName.module (Translation file not needed? Textdomain: wire--modules--inputfield--inputfieldpagename--inputfieldpagename-module)

But the file /wire\modules\Inputfield\InputfieldPageName\InputfieldPageName.module exists.

I have opened the json file with the translations I have observed that the attribute "file" is:

Wenn I use the translator manager to create a new translation file, the value of this parameter ist:

I have changed in all my language files the // by \/ and it works.

Can someone test if I'm wrong or this error are produced due to this wrong attribute in the translation files?

Thank you in advance.

Raul Garcia.

You're right. If you see other languages ​​appear \ / and no //. I'll fix it today :)

Gracias Raul 

Share this post


Link to post
Share on other sites

You're right. If you see other languages ​​appear \ / and no //. I'll fix it today :)

Gracias Raul 

I remember this behaviour. It depends on the PHP version. With php 5.5 (?) and higher you get the // when creating new translation files in the backend.

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...