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.

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

CLI syntax differs from xgettext #67

Closed
JustBlackBird opened this issue Aug 13, 2014 · 1 comment · Fixed by #70
Closed

CLI syntax differs from xgettext #67

JustBlackBird opened this issue Aug 13, 2014 · 1 comment · Fixed by #70
Assignees

Comments

@JustBlackBird
Copy link

Original GNU xgettext uses xgettext [option] <inputfile> syntax. At the same time jsxgettext uses jsxgettext uses jsxgettext <inpfile> [options], thus the two utilities have incompatible syntax.

@BYK BYK self-assigned this Aug 19, 2014
@BYK
Copy link
Collaborator

BYK commented Aug 19, 2014

Thanks for reporting, I'll see what I can do :)

BYK added a commit that referenced this issue Aug 20, 2014
BYK added a commit that referenced this issue Aug 20, 2014
BYK added a commit that referenced this issue Aug 21, 2014
Switches the option parser to
[visionmedia/commander.js](https://npmjs.org/package/commander)
from nomnom to fix #67, #68.
BYK added a commit that referenced this issue Aug 21, 2014
Switches the option parser to
[visionmedia/commander.js](https://npmjs.org/package/commander)
from nomnom to fix #67, #68.
BYK added a commit that referenced this issue Sep 2, 2014
Switches the option parser to
[visionmedia/commander.js](https://npmjs.org/package/commander)
from nomnom to fix #67, #68.
@BYK BYK closed this as completed in #70 Sep 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants