Closed ideasman42 closed 7 years ago
It seems that "POT-Creation-Date: YEAR-MO-DA HO:MI+ZONE\n"
is not a proper format.
Please provide decimal numbers for each YEAR
, MO
, ... to fix the problem.
@shimizukawa - right, however this is something that must have been written automatically by some PO translation software (it applies to all files), will have to contact the author. Also as far as I can see this meta-data could be ignored?
It would be useful for us to have the option in sphinx-intl to demote errors in single PO files to warnings (skipping the problematic PO files), so a badly formatted PO file would warn - just as syntax errors in RST files don't prevent sphinx from creating output.
Do you mean you already have found a concrete solution? It seems that the error caused from babel library and I can't find "ignore wrong meta-data", unfortunately.
@shimizukawa, no solution yet (besides local hack to babel not to read time&date metadata).
I've contacted the translator so they can resolve this. However this seems to be a re-occurring problem for us when new translators get involved.
Was thinking there could be an optional (off-by-default) demotion of errors to warnings around pofile.read_po(f)
in sphinx-intl.
For now, you and I have no solution. One option I think is: wrapping with try/except to hide traceback and indicate human-readable error message.
There is nothing to do from Sphinx's side. Now I close this issue but please feel free to resume at any time if you have some solution.
We have translations running on a server and if there is some inconsistency, error causes the build to fail.
I ran into a case where a PO file prevents the entire build from running:
PO file: