Re: [Po4a-devel]#278365: Found the issue, here is a workaround