#Poedit pro software#
Poedit is an efficient piece of software when it comes to editing gettext catalogs.
#Poedit pro update#
It is also possible to update from a POT file, or fill missing translation from TM (translation memory), set bookmarks and manage them, display quotes, entry IDs, notes for translators and sort items by file order, source and translation.You can clear an entire translation, copy from source, flag translation as fuzzy, show references and use a search function. Moreover, there are also some boxes, which can be used in order to input or edit text, as well as notes for other translators.
#Poedit pro pro#
Because Poedit 2 is a major upgrade, Pro features require a new license.
#Poedit pro install#
To translate the theme you need to follow these steps:įirst, download and install Poedit. And you should be able to translate the theme without any trouble.Īll of the contact form strings are translatable, what problem are you having with it? But it doesn’t mean it is an error or bug.Īs your pro said, it is a Warning. Many of the empty strings to translate are related to this. Whenever somebody creates a piece of software, it saves space for updates and modifications. Thanks for writing and for the kind words 🙂 I need to change the language of the contactform to Dutch and now it doesn’t work. Is there a fix for this? Can you help me out?
#Poedit pro code#
And if the theme has bugs - which calling gettext(“”) with an empty string is, a bug in the theme’s PHP code - Poedit cannot fix them by itself either. For example, if the theme doesn’t mark some strings as translatable, even though they should be, there’s no way Poedit could find them. The best it can do is to detect problems, but fixing them is something only the developer can do. It configures what needs to be configured and scans the theme for strings, as it did in your case.īut if the theme itself has bugs, there’s precious little that Poedit could do about it. You are right that Poedit Pro promises to do all the necessary things - for setting up the translation for a given theme or plugin.
Better yet, let the theme developer know about them (feel free to use my previous email) so that they can fix it. In that case you can just ignore the errors and click OK. Plus, it doesn’t really do anything (there’s nothing to translate in an empty string, after all), so it’s best to just use a plain string literal instead of wrapping it in a gettext function. in PHP code, you would get lot of gibberish text in place of the empty string when used with a translation. This means that whenever you use gettext(“”) or _(“”) etc. You see, the “” string is special in gettext - in PO files, the translations metadata are store as a fake translation of the empty string at the beginning of the file. I take it that you are the theme’s developer? If so, then the best fix is to not do this and fix the locations listed in the warnings. He gave me this answer:Īside from the less-than-ideal presentation of the errors by Poedit (I’ll fix this), what the warnings say is actually correct: the problem really is what it says, that the theme contains code to “translate” empty strings (“”) with gettext/PO, which doesn’t make much sense. (Sounds great) Only i got some errors and asked the Poedit developer what’s wrong. I’m trying to change to language file of the BBQ with Poedit Pro with the option that it changes everything in the theme automatically.
0 kommentar(er)
