Extracting Drupal 8 translations with POTX

Yeah it may be made to work without that with some static hackery based on file locations I guess. That may solve this for you. We *need* to maintain the 6.x branch for localize.drupal.org so it may be too painful to port the module already to D8 too and maintain 3 branches in parallel.

BTW the code parsing can parse D8 code fine as is happening on localize.drupal.org already :)

Yeah theoretically potx.inc and the drush stuff may be movable out to its own project that is versioned differently. We are busy with upgrading localize.drupal.org to D7 ATM and trying to avoid *nice to have" changes to cause less disruption in the process. Also potx.inc is a very ugly pile of procedural functions and @sebcorbin was/is working on making them more modern step by step. But once again after the l.d.o update happens :) That has been dragging on for years.

https://www.drupal.org/project/issues/search?issue_tags=Localize%20D7%20...

One needs to fix the code underlying the drush command then :)

Did #2357369: Don't use drupal_get_path() for loading server-side code from within POTX fix it then? :) With that there should be no need for an active Drupal install (or dependency on any Drupal version) for extraction anymore no?

#2475163: Load default patterns from potx folder and #2371765: Fatal error on Twig_Lexer using drush potx when used from 8.x codebase are also needed. With those everything worked for me. And with https://github.com/cocomore/drush_language I can import them via drush :))

To extract translatable string from Drupal 8 you:

• Setup ad D7 website, install and enable the 7.x-3.x potx module
• Apply the latest patch from #2371765: Fatal error on Twig_Lexer using drush potx when used from 8.x codebase
• From your D7 site run: drush potx single --api=8 --folder=/path/to/drupal8/root
• The files will now be written in the current directory to: general.pot

#2371765: Fatal error on Twig_Lexer using drush potx when used from 8.x codebase landed. We should ideally port the module to D8 too sooner or later. At least using the code in a D8 Drush environment may work given the version agnostic approach of potx itself and drush. Feedback / reports of success / failure welcome :)

If there would be a D8 version it would be on drupal.org.

I used this not long ago, here are my notes in case they are helpful:

For exporting the strings to pot template translation files:

1. Download potx module 7.x-3.x (yes, 7.x-3.x, there is no 8.x version and we can still use 7.x-3.x from the command line via drush).
   drush dl potx-7.x-3.x --package-handler=git_drupalorg
2. Run the following command for each module:
   drush potx single --include=modules/contrib/potx/ --modules=mymodule --api=8
3. This will generate a general.pot file in the running folder. Rename it to mymodule.pot.

See also #2611298: Port potx to Drupal 8.

Combined #16 & #18:

• remove .info and .install files
• create potx.info.yml:
  

  name: Translation template extractor
  description: Provides a web interface and an API to extract translatable text from the sources of installed components.
  core: 8.x
  package: Multilingual
  version: 8.x-1.x-dev
  dependencies:
    - locale
  type: module
  

• drush dl potx-7.x-3.x --package-handler=git_drupalorg
• drush en potx
• drush potx single --include=modules/contrib/potx/ --modules=mymodule --api=8

Output will be stored in the Drupal root.

#21
Do you download the module globaly (within ~/.drush) or localy (on the website) ?

Hi! Thanks for the previous comments on this issue. I was following the comments set in #16 and #18 (merged in #21) But I'm getting the following error :

PHP Fatal error: Call to undefined function drupal_get_path()

From the drupal root I'm running :
drush potx --include=./modules/contrib/potx/ --modules=my_module --api=8

Am I doing something wrong? Because drupal_get_path() is still in core.

Thanks!

I did a quick'n'dirty port of the module in order to make it works out of the box with drush on drupal 8 :

1. download this module in modules folder (if you use composer : composer require kgaut/potx)
2. enable it : drush en potx
3. extract translations with drush : drush @ALIAS potx single --include=modules/contrib/potx/ --modules=MYMODULE_MACHINE_NAME --api=8

Thanks to #16 #18 and #21.

https://github.com/kgaut/drupal-potx

Following what Kgaut wrote in #24:

• download the potx from #24 (https://github.com/kgaut/drupal-potx) to modules/contrib/potx/
• drush en potx
• extract translations with drush but without the --include (and without ALIAS):
  drush potx single --modules=MYMODULE_MACHINE_NAME --api=8
  (with --include I got the "undefined function drupal_get_path()" error)

I managed to generate a general.pot.

If I remember correctly older potx-Versions where able to generate *.po files, which included the existing translations (pot is the template file).

How can I get the .po nowadays?

@gngn : by renaming the *.pot file to *.po, I was able to translate it and import it back.

Even-if it's not the proper way, it works.

@Kgaut: thanx - but this way I do not get the already existing translations...

Yes, any possiblity to extract existing translations?

Lets standardized the efforts here.

Do the current maintainers have any plans to port the module, or might they be willing to let someone help?

Help would be really appreciated. Although, a backlog of issues have been built up that I need to look into first. So, it will probably take around one or two months before I can come up with a plan for porting to Drupal 8.

I did a even-more-dirty modification to be able to include the translations from the database

https://github.com/kgaut/drupal-potx/pull/2

so now you can do
drush potx single --modules=MYMODULE_MACHINE_NAME --api=8 --language=es

And the translations will be included. This is very valuable for our workflow.

Thanks rodrigoaguilera ! I've just merged it and updated the readme :

Thanks to @rodrigoaguilera you can now export tranlated string from the database : drush @ALIAS potx single --modules=MYMODULE_MACHINE_NAME --api=8 --language=es

https://github.com/kgaut/drupal-potx

FWIW, this crashes for me because it tries to access a nonexistent languages table. This is on a single language, non-english 8.x-3.x-beta1 site.

The mechanism in #16 using an underlying D7 site works fine, however.

#33 works for me (8.2.6).

@fmfpereira: are you on a single-language non-english site ?

@fgm: yes. I have portuguese as default language and english.

So that's probably why it works: I guess the languages table is not installed on single-language sites.

I run into the same issue as #34 on 8.2.7: no languages table.

I read a bit the code and I think it only uses the language table to get the number of plurals.

We can easily change that line for a call to
https://api.drupal.org/api/drupal/core%21modules%21locale%21src%21Plural...

The line is
https://github.com/kgaut/drupal-potx/blob/8.x-1.x/potx.inc#L614

Can someone confirm that is the conflicting line?

I'm updating the issue title as it's totally differently focused now.

For the port itself, per #19 we could use #2611298: Port potx to Drupal 8.
@herom, I'm quite interested on moving this forward, so if I can help let me know what's needed for shaping up the plan.

Created https://github.com/kgaut/drupal-potx/pull/5 for the problem with monolingual English sites reported in #34 and confirmed in #39.

#42 is merged in https://github.com/kgaut/drupal-potx

Thanks

@penyaskito, Here is the plan right now:

First of all, we should finish the basic port to Drupal 8, which is handled in #2611298: Port potx to Drupal 8. There are some hooks and forms that need to be ported right now.

The patch to allow exporting translations from the database should be added in #2175955: Support language dependent content and translations export in Drush command, although there should be a note that the translations will be extracted from the drush Drupal installation, not from the destination.

And the missing languages table fix should be added to this issue. Although, the current code using db_table_exists() causes a big slowdown, and its results should be cached somewhere.

how to use this command in drupal 8.6.x.

drush potx single --include=./modules/contrib/potx/ --modules=mymodule --api=8

it report an error. potx is not defined.

fixed it.

Drupal 8.6.x potx not work?

1. 使用这个模块替换原有7.x版的模块代码—git@github.com:kgaut/drupal-potx.git
2. drush en -y potx
3. 使用该命令进行翻译文件导出。
./vendor/bin/drush potx single --include=modules/contrib/potx/ --folder=modules/mymodules/ --api=8

I've updated issue summary with the actual problem reported in comment #20.

The reason for missing translatables from config/install is that extracting these pots requires their schemas to be present.

so issue summary updated again to comment #44.

what is missing languages table?

oh that close was a mistake