poedit | Translations editor for Mac , Windows and Unix | Internationalization library

Well, I finally found the solution:

The gettext extensions loaded for CLI SAPI:

$ php -r "echo gettext('hello');"

Web SAPI haven't it: search on the phpinfo page compile flag --with-gettext[=DIR]

1. Find extension dir: php -i | grep extension_dir (example extension_dir => /usr/lib/php/20190902 => /usr/lib/php/20190902 )
2. Find the gettext extension path: find /usr/lib/php/20190902 | grep gettext (example /usr/lib/php/20190902/gettext.so)
3. copy extension from cli dir to web dir: cp /usr/lib/php/20190902/gettext.so /extension_dir_path
4. reload web server

See the File → New from PO/POT file… menu.

I believe the confusion is that you're using a dynamic domain, based on the language, while the domain is fixed and represents the filename of the translation.

So first of all, reorganise your files as follows

I solved the problem with the following steps:

• First, Open Poedit and go to File->preferences

• Second, Click on the Extractors Tab and add a custom extractor with the plus sign on the bottom. Mine is already created as you see in the picture.

• Finally add the following values to the relevant fields:

Field 1 = PHP

Field 2 = ‪*.php;.html;.html5

Field 3 = xgettext --language=PHP --add-comments=TRANSLATORS: --force-po -o %o %C %K %F

Field 5 = ‪%f

And that is it. Hopefully you can now add your html or html5 file paths in the catalogue properties and enjoy the Poedit extraction features without any problem.

Here's how I "solved" the problem: I completely deleted the i18n and did everything again (in the exact same way). For some reason, it does work now.

Best Practice is to not translate in form Type class. Try to put untranslated tag there, and translate in template. This not resolve problem with autogenerate '.po' files, but simplifies Type class, ie. not need to inject translator, not need to translate in every FormType class with title attribute field. Otherwise it requires to put translator and translate attributes in every Type class in the future.

Translate form filed attribute in template, require overloading build-in form template as described in Creating your Own Form Theme.

To simplify process in this case:

• Copy block widget_attributes from build-in template thatis used to own clean template. ie.: templates/form/my_theme.html.twig

• Add dthis template to config/packages/twig.yaml in tag form_themes, ie.:

It is not possible.

And since it would require a major change to the extractor logic to make the comment placement more flexible, it is highly unlikely that this will ever change.

If it is mission-critical for you: Preparse your sources with a little script, and if you find #TRANSLATORS comments, extract them into a line above the invocation of _().

I propose an extension of models res.partner.title and res.partner.

res.partner.title should get a translateable field for saving salutation prefixes like 'Dear' or 'Sehr geehrter' (German). Maybe it's worth to get something about genders, too, but i won't get into detail here about that. You probably want to show the configuring user an example like "Dear Mr. Name" or something like that. A computed field should work.

On res.partner you should just implement either a computed field or just a method to get a full salutation for a partner record.