Error Errors Happened While Running Gettext On
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow msguniq windows the company Business Learn more about hiring developers or posting ads with us Stack
Install Msguniq
Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community
Msguniq: Command Not Found
of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Windows Error: errors happened while running xgettext on __init__.py ,'xgettext' is not recognizad as an internal or
Xgettext: Command Not Found
external command up vote 1 down vote favorite 1 when running django-admin.py makemessages -l fa based on internationalization documentations in windows i get this error: Windows Error: errors happened while running xgettext on __init__.py ,'xgettext' is not recognizad as an internal or external command what should I install and which variables add to environment?I googled alot but just found a japanese references!! python django share|improve this question asked Nov 18 '11 at brew gettext 10:43 Asma Gheisari 89511634 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted This is covered in the documentation. share|improve this answer answered Nov 18 '11 at 10:53 Daniel Roseman 321k23403486 I downloaded both of them(gettext-runtime-X.zip,gettext-tools-X.zip ) and extracted their bin folder contents ino this path:C:\Program Files\gettext-utils\bin and added this path to system path.but I have the same problem –Asma Gheisari Nov 18 '11 at 14:32 1 I downloaded it's Installation version from this address and it worked : sourceforge.net/projects/gnuwin32/files/gettext/0.14.4/… –Asma Gheisari Nov 19 '11 at 11:29 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged python django or ask your own question. asked 4 years ago viewed 1386 times active 4 years ago Related 0bug in “django-admin.py makemessages” or xgettext call? -> “warning: unterminated string”11Django MakeMessages missing xgettext in Windows3Incomprehensible Django Runserver Error2Django “__init__() keywords must be strings” error while running “runserver”65'pip' is not recognized
Sign in Pricing Blog Support Search GitHub This repository django makemessages Watch 105 Star 1,284 Fork 558 Fantomas42/django-blog-zinnia Code Issues install brew 10 Pull requests 0 Projects 0 Pulse Graphs New issue Error: errors happened while running xgettext When I django-admin.py makemessages -l #53 Closed pykhmer opened this Issue Dec 19, 2010 · 1 comment Projects None yet http://stackoverflow.com/questions/8181143/windows-error-errors-happened-while-running-xgettext-on-init-py-xgettext/8181254 Labels ICC Milestone No milestone Assignees No one assigned 2 participants pykhmer commented Dec 19, 2010 F:\Python27\Lib\site-packages\django-blog-zinnia\zinnia>django-admin.py makemessages -l km processing language km Error: errors happened while running xgettext on init.py 'xgettext' is not recognized as an internal or external command, operable https://github.com/Fantomas42/django-blog-zinnia/issues/53 program or batch file. How to fixed this problems thanks Owner Fantomas42 commented Dec 20, 2010 Gettext is not installed. Read the django's doc about that : http://docs.djangoproject.com/en/1.2/topics/i18n/localization/#gettext-on-windows Note : for support I have a google group http://groups.google.com/group/django-blog-zinnia/ so don't flood the issue tracker with that. The tracker is designed to collect suggestions/patches/bugs no support issues ! Have a nice day This issue was closed. Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Terms Privacy Security Status Help You can't perform that action at this time. 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.
Previous TicketNext Ticket → Opened 4 years ago Closed 4 years ago #18479 closed Cleanup/optimization (fixed) xgettext warnings cause the makemessages command to raise an exception Reported https://code.djangoproject.com/ticket/18479 by: anonymous Owned by: Claude Paroz Component: Internationalization Version: 1.4 Severity: Normal Keywords: Cc: niels.busch@… Triage Stage: Accepted Has patch: no Needs documentation: no Needs tests: no Patch needs improvement: no Easy pickings: no UI/UX: no Description Related to ticket #7564, in that the messages thrown are the same. System: Macbook Pro, command not Lion OS, Django 1.4, Python 2.7.3, xgettext 0.18.1 Still seeing the error: Error: errors happened while running xgettext on models.py ./myproject/models.py:177: warning: 'msgid' format string with unnamed arguments cannot be properly localized: The translator cannot reorder the arguments. Please consider using a format string with named arguments, and a mapping instead of command not found a tuple for the arguments. This happens because xgettext will still throw a warning, which will be catch by the "if errors:" block in makemessages.py. Inside the block, we will then raise an exception, regardless of whether or not this error is a fatal error or not. Suggest fix to at least look at the error level (info,warning, error, etc.) and only raise an exception if the error is fatal. Oldest first Newest first Threaded Show comments Show property changes Change History (5) comment:1 Changed 4 years ago by baokham.chau@… Needs documentation: unset Needs tests: unset Owner: changed from baokham.chau@… to anonymous Patch needs improvement: unset comment:2 Changed 4 years ago by Claude Paroz Triage Stage: Unreviewed → Accepted Type: Uncategorized → Cleanup/optimization Agreed, we should only raise CommandError if the status code of the executed command is != 0. The _popen function should get and return p.returncode. comment:3 Changed 4 years ago by Ni