Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

XLIFF Wrong file extension #128

Closed
goetas opened this issue May 28, 2013 · 4 comments
Closed

XLIFF Wrong file extension #128

goetas opened this issue May 28, 2013 · 4 comments

Comments

@goetas
Copy link
Collaborator

goetas commented May 28, 2013

XLIFF specifications recommends .xlf as file extension, the current implementation uses .xliff

The generated files are incompatible with some tools like pootle.

Oasis Specification:
http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.pdf (page 70)
@carlcraig
Copy link
Contributor

I think you can get round this by adding the --output-format=xlf parameter to the translation:extract command.

Or in the configuration add output_format: xlf to a specific configuration setup.

@goetas
Copy link
Collaborator Author

goetas commented Jun 21, 2013

Using --output-format=xlf will fallback to Symfony XLIFF dumper.
But JMSTranslationBundle/Translation/Dumper/XliffDumper has a more complete implementation than Symfony XLIFF dumper

@carlcraig
Copy link
Contributor

Ok, I see what you mean here, the XLIFF dumper in translation bundle is much more complete

@carlcraig carlcraig mentioned this issue Jun 21, 2013
Merged
@carlcraig
Copy link
Contributor

This can be closed now @schmittjoh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@schmittjoh @goetas @carlcraig