You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the destdir option is given explicitly as a command line argument (po4a po4a.cfg --destdir out), the problem doesn't occur; the translations are not created in the current directory:
.
├── out
│ ├── foo.txt
│ └── po
├── po
│ ├── all.pot
│ └── ja.po
├── po4a.cfg
└── src
└── foo.txt
Thanks @gemmaro for this very good bug report. Your test case and analysis were really helpful. I would have difficulties to spot the issue if you didn't mention that providing the options on the command line were fixing the problem.
For example, when the files are located as:
and
po4a.cfg
is like:then after runnning
po4a po4a.cfg
:If the
destdir
option is given explicitly as a command line argument (po4a po4a.cfg --destdir out
), the problem doesn't occur; the translations are not created in the current directory:Here is a repository to reproduce: https://github.com/gemmaro/po4a-issues-420
Tested po4a versions: 0.68, 0.69.
The text was updated successfully, but these errors were encountered: