You might have just needed to reload your terminal.
Did you finely made it on windows ?
I still have an error âThe syntax of the command is incorrectâ even after installing coreutils, findutils and gettext
Thanks
No, Iâm using Polylang so it wasnât necessary. But in the long run Iâll setup Hackintosh because there is just too much trouble with Roots and windows or web dev in general.
Thanks for yout feedback.
Well, any help from the community would be appreciated to make it work on windows
Iâm getting the same error message on WSL:
xargs: xgettext: No such file or directory
Now I donât really know my way around Linux but this seems to work:
I noticed that:
/usr/local/opt/gettext/bin
Doesnât exist on my Ubuntu 18.04 WSL Installation. In fact, there is no â/opt/â directory at all.
The closest thing folder I could find is here:
/home/linuxbrew/.linuxbrew/Cellar/gettext/0.19.8.1_1/bin
So I ran this command instead of the above PATH command:
echo âexport PATH="/home/linuxbrew/.linuxbrew/Cellar/gettext/0.19.8.1_1/bin:$PATH"â >> ~/.bash_profile
And then restarted the WSL terminal.
Now yarn pot seems to run fine, asides from a couple of âunterminated stringâ warnings in my blade files.
Itâs probably not a great solution so if anyone can figure out why I donât have â/opt/gettext/bin/â then please let me know.
Iâm running into the same issue on Windows. Yarn pot script fails with an exit code 1 (Incorrect syntax).
Any help would be greatly appreciated. Thanks.
For me, this still returns
xargs: xgettext: No such file or directory
error Command failed with exit code 127.
Any help appreciated.
ps: tried
echo 'export PATH="/usr/local/opt/gettext/bin:$PATH"' >> ~/.zshrc
(using oh my zsh)
and reloading, it works.
Hi, Iâm on Windows and I do have the same problem.
Did you find a solution ?
I use WSL 2 now, hence all *nix/Ubuntu tools can be used.
Ok thx, I used Wp-cli
My script : âpotâ: âwp i18n make-pot . resources/my-theme.potâ
Every yarn pot launch an update on my-theme.pot and generate my translation automaticly.
That my client can then used in locotranslate plugin.
I also use VSCode with WSL 2 remote extension. The build is much faster, and the site (Docker) also runs much faster on native WSL 2 *nix file system.