Manfred62 Posted August 9, 2014 Share Posted August 9, 2014 (edited) for the upcoming PW version 2.5: here you find a list of files which I have translated (based on the actual dev pre 2.5). These are 122 files (updated). Not all have to be translated, but are "nice to have". If someone wants to start a new lang-pack, take the empty lang files from the zip. list of all files: 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--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--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--adminthemereno--adminthemereno-module.json wire--modules--admintheme--adminthemereno--adminthemerenohelpers-php.json wire--modules--admintheme--adminthemereno--debug-inc.json wire--modules--admintheme--adminthemereno--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--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--templates-admin--debug-inc.json wire--templates-admin--default-php.json empty lang pack: pw-lang-empty-2.5.zip EDIT: thanks to Nico/Ryan. Updated the lang pack. Now includes 122 files. Edited September 13, 2014 by Manfred62 10 Link to comment Share on other sites More sharing options...
Christophe Posted September 4, 2014 Share Posted September 4, 2014 Hello, Nice Job! Wouldn't it be easier for everyone to have something like a language pack in the default language of Processwire in an official git repository (I'm just starting to learn it) that would enable to see changes and also ease translations? Link to comment Share on other sites More sharing options...
jtherczeg Posted September 4, 2014 Share Posted September 4, 2014 I would prefer to move the translation process to an online collaborative tool, like Transifex. Anyway, in the upcoming version 2.5, available in the dev branch on GitHub, many language translation and localization enhancements were made, see recent blog posts Language Translation Updates and More Language Updates. Besides this, in the case of languages using accented characters and diacritical marks, not so easy to translate such language file side by side in a diff tool, like WinMerge, because the accented characters are encoded to hexadecimal Unicode characters, e.g. ä is displayed as u00e4. 1 Link to comment Share on other sites More sharing options...
Pierre-Luc Posted September 5, 2014 Share Posted September 5, 2014 jtherczeg, I clicked on this thread to propose exactly that — using Transifex. As far as I know Transifex works best with typical gettext files but I wonder how/if this could be adapted to work with PW's JSON files. 2 Link to comment Share on other sites More sharing options...
jtherczeg Posted September 6, 2014 Share Posted September 6, 2014 Pierre-Luc, Transifex supports several file formats, including JSON keys-values, however, I'm afraid the files should be converted to the correct format. Link to comment Share on other sites More sharing options...
Manfred62 Posted September 13, 2014 Author Share Posted September 13, 2014 the "empty lang pack" is updated --> contains 122 files now. Based on the pre 2.5 version of PW from 13 September 2014. 1 Link to comment Share on other sites More sharing options...
apeisa Posted September 13, 2014 Share Posted September 13, 2014 Is there any reason for empty lang pack now that PW scans all lang files? 1 Link to comment Share on other sites More sharing options...
Manfred62 Posted September 14, 2014 Author Share Posted September 14, 2014 Is there any reason for empty lang pack now that PW scans all lang files? no, not really anymore. But PW also scans some files that should not or cannot be translated. So I think it's a little bit easier for new translators to take this prepared empty pack. 1 Link to comment Share on other sites More sharing options...
lisandi Posted November 8, 2014 Share Posted November 8, 2014 Have a look here https://processwire.com/talk/topic/3317-get-localization/?p=79537I think that way woudl help Processwire a lot and would reduce the workload for each one of us here too as we woudl be able to collaborate and benefit from a mmuch more and better translatable processwire.One way woudl be to upload all those files to Pootle but much better woudl be to start keeping translations in a separate file. Link to comment Share on other sites More sharing options...
Soma Posted November 8, 2014 Share Posted November 8, 2014 Its much easier to use in place translation with the gettext method as it is now. Adding an extra file with translation complicates things and add overhead where not needed translations would be loaded. Link to comment Share on other sites More sharing options...
lisandi Posted November 8, 2014 Share Posted November 8, 2014 It is not atall an overhead as not needed translation simple does not get loaded - like itis at TYPO3. Only translatins really needed and only from those modules installed gets loaded and also here you can translate the files afterwards inside the backend and still can do individual smaller adjustments which even stay when you update all the rest of your files.There are 2 major problems with translations: 1. You need to keep translations updated with the core and module files, which means this is not a one time job!2. Translating stuff takes a lot of time, so it is nonsense to waste time in doing that job over and over again for each site of all developers who develop a site in the same language with processwire. Have a look to how it is done in a professinal way! https://processwire.com/talk/topic/3317-get-localization/?p=79537and check out Pootle - it would make things so much easier for all of us! Link to comment Share on other sites More sharing options...
Soma Posted November 8, 2014 Share Posted November 8, 2014 I'm not sure were on the same page, but having translation in one file means on each request it load and translates the files even if not needed. You don't seem to grasp the why it is a overhead and gettext is an approach that has pros and cons, so has other ways of translation approaches. We already know that and it's been discussed already. It's not that we have no idea about all this. Link to comment Share on other sites More sharing options...
Pete Posted November 8, 2014 Share Posted November 8, 2014 Lisandi: you have linked to that post about pootle four times from different topics now in the space of a few hours. Please stop doing this as it is spamming. If people want to contribute to your discussion about pootle then they will but linking to it four times because you think it is important is spamming. Link to comment Share on other sites More sharing options...
lisandi Posted November 9, 2014 Share Posted November 9, 2014 hi pete There are 4 Threads talking about the same stuff and that is why it is usefull to link them to one of those threads and actually to close those other Threads. This is a job for a Forum Admin or Moderator than only one Thread would exist and not four. If only one thread exists or if all threads which open up the Theme again would go to the same first thread discussions can stay together and be fruitful instead of having to search for solutions in lots of same threads. It is not at all spamming! it is helping people to find a solution. do your job as admin and this won't be necessary! Link to comment Share on other sites More sharing options...
marcus Posted November 9, 2014 Share Posted November 9, 2014 (edited) lisandi, just a piece of advice: continuing in behaving like you do at the moment, always and kind of aggressively advising the same service, and to talk smack to moderators won't make you any friends here. Edited November 11, 2014 by marcus 3 Link to comment Share on other sites More sharing options...
Pete Posted November 9, 2014 Share Posted November 9, 2014 I have nothing more to add here except to say that I have made my position clear and that we have now posted clear Community Rules & Guidelines in our News & Announcements forum. If anyone has any issues whatsoever, please refer to that topic to determine the appropriate course of action. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now