Jump to content

Polish (pl-PL)


PawelGIX
 Share

Recommended Posts

This is my first post so, Hello everyone.

Ryan, I want to congratulate a great CMS.

I attach my translation for the Polish language.

The translation is fairly complete, but it requires some adjustments.

Hidden deeper setting are not yet translated.

And also the Polish translation for TinyMCE.

TinyMCE will not work without it.

https://github.com/PawelGIX/ProcessWire-Language-Pack-Polish--pl-PL-

EDIT:

I added a link to github.

ProcessWire-Language-Polish.zip

tinymce_language_Polish.zip

  • Like 2
Link to comment
Share on other sites

  • 4 months later...
  • 2 months later...

Thanks for making polish language pack

I found a little problem with it. When it's activated, TinyMCE isn't showing up and here are the errors from Chrome:

Failed to load resource: the server responded with a status of 404 (Page Not Found) http://process...pl/wire/modules/Inputfield/InputfieldTinyMCE/tinymce-3.4.7/langs/pl.js
Failed to load: http://process...pl/wire/modules/Inputfield/InputfieldTinyMCE/tinymce-3.4.7/langs/pl.js tiny_mce.js:1
Failed to load resource: the server responded with a status of 404 (Page Not Found) http://process...pl/wire/modules/Inputfield/InputfieldTinyMCE/plugins/preelementfix/langs/pl.js
Failed to load: /wire/modules/Inputfield/InputfieldTinyMCE/plugins/preelementfix/langs/pl.js tiny_mce.js:1
Failed to load resource: the server responded with a status of 404 (Page Not Found) http://process...pl/wire/modules/Inputfield/InputfieldTinyMCE/tinymce-3.4.7/themes/advanced/langs/pl.js
Failed to load: http://process...pl/wire/modules/Inputfield/InputfieldTinyMCE/tinymce-3.4.7/themes/advanced/langs/pl.js

Adding polish translation to TinyMCE from this link to /wire/modules/Inputfield/InputfieldTinyMCE/tinymce-3.4.7/ didn't help. What helped was removing the language reference in Setup > Languages > Polish > wire--modules--inputfield--inputfieldtinymce--inputfieldtinymce.json as ryan advised.

Link to comment
Share on other sites

I wish that TinyMCE had a more graceful fallback for when a language file wasn't present. It seems like they way they are doing it is not right.

What helped was removing the language reference in Setup > Languages > Polish > wire--modules--inputfield--inputfieldtinymce--inputfieldtinymce.json as ryan advised.

Glad that worked, thanks for letting me know.

Link to comment
Share on other sites

  • 1 year later...
  • 3 years later...

Hello, in the last couple of days I've built a complete new Polish translation for the ProcessWire 3.0.63.

It may need some cleanup of typos, some translations were done without the context, as I'm new to ProcessWire, so those may need corrections.

Anyway, all language files reported by Processwire (168) and all contained phrases were translated.

@PawelGIX, I hope that you don't mind that I post here, but I don't want to open a new topic if topic about Polish translation already exist :)

@Ryan and everyone involved, thanks for building this great CMS!

Github repo:
https://github.com/sevenstudio/polish-wire

ZIP package also attached to this post.

I hope this will be usefull for Polish users of PW.

Bug reports, suggestions are welcome!

Thanks!
Tomasz

 

 

polish-language-pack-ProcessWire-3.0.63.zip

  • Like 1
Link to comment
Share on other sites

  • 2 months later...

@rafaoski

You're welcome! I hope it will be useful.

I've submitted new Polish language pack (for 3.X) to the official modules directory at ProcessWire, it's still pending approval, but I hope it will be approved soon. If you will find any bugs, typos, please let me know and I will try to update it.

Thanks!

Pozdrawiam ;) !

  • Like 1
Link to comment
Share on other sites

  • 1 month later...

Hello guys,

I would like to inform that I've updated my polish translation for PW 3.x to version 1.0.1

This version should be fully compatible with the latest PW dev version 3.0.77 as well with latest stable release.

In this update:

- new translation files were added for new features like new fieldset field, or import/export features

- there is also a complete translation file for the new login/register/profile module, created by @ryan in the last week

- other than that, I've corrected few small typos, few phrases were changed.

Complete polish translation for 3.x is now available in the official modules directory:

http://modules.processwire.com/modules/polski/

bug reports, typos, suggestions are welcome!

  • Like 2
Link to comment
Share on other sites

Hello, I've updated language pack to v1.0.2.

New update contains fixes of wrong paths in translation files. This version should work correctly with all operating systems (in case that you have problems on unix servers).

You can grab the latest version in modules directory
http://modules.processwire.com/modules/polski/
or directly at github repo.

 

 

Link to comment
Share on other sites

  • 2 months later...

I would like to inform that the Polish language pack for PW 3.x was just updated to version 1.0.3.

In this update:
- translated all new strings
- fixed few typos
- some translations were changed, to suit better with the context


Language packaged should be fully compatibile with the latest PW releases including latest dev. version - 3.0.84

You can grab latest version of this language pack directly at Github or from the official PW modules directory.

As always, feedback, bug reports are welcome!

Link to comment
Share on other sites

  • 3 months later...

Hello,

I've just updated my polish language package to version 1.0.4.

In this update:
- added missing translations for all new features
- because there is a new master version of PW 3.0.96, in this version I've decided to removed all translations that were marked as "abandoned" since last release.

Grab latest version from the official modules directory:

http://modules.processwire.com/modules/polski/

or direrctly at github:

https://github.com/sevenstudio/polish-wire/releases

As always, bug reports/suggestions are welcome,

Thanks

  • Like 1
Link to comment
Share on other sites

  • 4 months later...

Hi,

I've updated language pack to version 1.0.5.

This version is fully compatibile with the latest master version 3.0.96 and the DEV version 3.0.108.

This version contains translated all new features introduced since release of the latest master version + full translation of the new UIkit admin theme.

Download driectly at github:

https://github.com/sevenstudio/polish-wire/archive/1.0.5.zip

or from the official modules directory:

http://modules.processwire.com/modules/polski/

Tomasz

  • Like 1
Link to comment
Share on other sites

  • 4 months later...

Hello @7Studio!

I was just curious if there is a newer translation and here we are.
Tomek, great job, all is working fine (PW 3.0.98 on localhost).

I can see that there are still some phrases in English. I don't know if this has been your choice to leave them like that or was it rather lack of need / time.
I'm a newbie here (just converting from WordPress after almost a decade) and still learning everything,
but after few weeks I'm planning to build a bigger site with PW and there will be several places that will have to be in Polish.
If you need some help with translating - let me know.

Pozdrawiam ciepło,
Krzysztof
 

  • Like 1
Link to comment
Share on other sites

Hello @phoros,

thanks a lot, glad to hear that translation is useful!

Regarding to the missing strings, phrases - overall I'm trying to keep 100% of core translated. Some elements, like the core modules descriptions are keept in english.

Please note that some translations are also changed during dev versions, some strings are added/changed, some are abandoned, so it also depends which version you are running at the moment. (I've decided to remove many abandoned translations with latest update, but they may be used in older versions).

I'm keeping eye on the development, and since we are really close to the next master version (according to Ryan latest post), I'm plannig to release an update (1.0.6) that should be 100% compatibile with latest master version.

At the moment I don't need help (thanks anyway!), but if there will be a new version I will be thankfull for reports if anything is missing.

Have a fun while working with ProcessWire! 😉

Pozdrawiam!
Tomek

Link to comment
Share on other sites

Wonderful!

I've found out lately that the translation depands also on a UI administration theme -
when default is used it's all translated but with UIkit theme there are several places in English.
I assume that it needs to be translated elsewhere (if necessary).

For me it's better to work in English but for clients / authors it's of course unacceptable.
So once again - thanks a lot!

Last weekend I've shown PW few guys in two companies and explained the idea.
They are very intrigued and one of them is planning to try it for building a PHP/MySQL app
for their company administration. So it's good to know that we don't have start from scratch with translating.

Wielkie dzięki i pozdrawiam serdecznie!
Krzysztof

Link to comment
Share on other sites

Translations in new UiKit admin theme depends on the session, so you may want to try to logout and login once again after switching admin theme and clean your web browser cache.

The new UiKit admin theme was completly translated with version 1.0.5 (I've just checked with latest dev version and I don't see any missing strings there), so there is a chance, that you are using older version of the language pack - v1.0.4.

You can try to upgrade to the latest DEV version (dev. versions in PW are extremely stable), and reinstall language package.

Small tip, while browsing translation files in: settings - languages -> your language, you can double click trash icon to select all files, after that click on save to delete them and please try to install latest version of language package 1.0.5.

As I've mentioned above you will need to clear sessions, (logout) and browser cache to get UiKit theme fully translated.

I've also clients sites on PW so I try to keep this translations up to date 😉

Please let me know if reinstalling language package helped with UiKit theme translations.

Pozdrawiam sedecznie!
Tomek

 

Link to comment
Share on other sites

You were right of course - after upgrading to 3.0.122 (from 3.0.98),
everything is displayed correctly in Polish (see the attachment) and works like a charm.
Relogging after changing a language also does the trick. Thank you!

I'm learning to walk here so please forgive me lack of knowledge.

Now I'll try to play around with modifing a ready HTML/CSS/JS template
and connecting it to PW.

No new projects and no deadlines so far
so I can climb that hill at my own pace. One step in a time. 😎

Jeszcze raz bardzo dziękuję za pomoc i pozdrawiam ciepło.
Krzysztof

admin_PL.jpg

Link to comment
Share on other sites

  • 3 weeks later...

I would like to inform that my polish language pack was updated to version 1.0.6.

This version should be fully compatiblie with the latest master version of ProcessWire - 3.0.123

Download driectly at github:

https://github.com/sevenstudio/polish-wire/archive/1.0.6.zip

or from the official modules directory:

http://modules.processwire.com/modules/polski/

  • Like 1
Link to comment
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
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Similar Content

    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more.
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWire to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. See a solution below... No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is a long-standing issue in the larger web development community and creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Enhancements
      Translate All Fields On A Page
      An exciting companion module has been written by @robert which extends the functionality of Fluency to translate all fields on a page at once. The module has several useful features that can make Fluency even more useful and can come in handy for translating existing content more quickly. I recommend reading his comments for details on how it works and input on best practices later in this thread.
      Get the module at the Github repo: https://github.com/robertweiss/ProcessTranslatePage
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost. Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By hellerdruck
      Hi all
      I need to export all the texts from a website to a translation company (as json or csv or txt...). How can this be done? Of course manually, but this website is huge and it would take me years...
      Also, as a second step, importing the translation ...
      Any ideas anyone? Tutorials? Plugins?
      Thanks for your help.
    • By snobjorn
      Here's my Norwegian language pack for ProcessWire. I've been adding translations gradually since 2015. By November 2020 the translations are completed, and up to date with the latest dev version of ProcessWire.
      For details, go to the ProcessWire Modules page …
      https://modules.processwire.com/modules/norwegian/
      … and/or GitHub:
      https://github.com/snobjorn/processwire-norwegian-language-pack-nb-no
      Status:
      Completed / up to date.
      Third party and PRO module translations have moved to another repository:
      The site files have been moved to a new repository for module files in Norwegian. Those translations includes translations for some free and some pro modules, see the complete list at GitHub.
    • By bartelsmedia
      "Deepl" is an unbelievably good (paid) text translation service, that mops the floor with Google Translate.
      They have an API and it would be awesome, if there would be a module, that would integrate it for easy content translation.
      It could be a right-click context menu on the language tab:

      It should ask from which of available other language it shall take translate from.
      What do you think?
    • By gregory
      Hi guys, I need help.
      how do I translate Next Page?
      <?php if($page->next->id) {echo "<div class='float-right'><a class='button' href='{$page->next->url}'> Next Page </a></div>";} ?> I usually use this:
      <?php $lang = $user->language->name; if($lang == 'default') {echo "Next Page";} else {echo "Pagina successiva";} ?> or
      <?php echo __("Next Page"); ?> Thanks
×
×
  • Create New...