-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Problem with non-acsii userprofile name on Windows (7) #297
Comments
Why didn't this got any attention? This is an important issue. I cannot use node-gyp because my name is João, and I'm not going to create another user just for compiling purposes... |
I did (because of too often similar issues) :) But of course , this is very bad solution.. |
I was refering that its not pratical to change users each time I need to update or install a package that needs node-gyp. I ended up copying the .node-gyp directory created in my home dir to other place and passed the --nodedir flag. Of course it will not work with npm install, but its better than keep changing users. |
One of the beauties of open source is if the problem really annoys you, you are fully empowered to fix it! There's a lot of work needed to fix issues in node-gyp, so I'm not personally going to be able to investigate this in the near future. Could one of you do the investigation, make a fix, and submit a pull request? @danyaPostfactum @jfhenriques |
Hy @JayBeavers I submited a pull request that still needs some work. At least now it works for me, but it might break for others. Please take a look at #366 |
@jfhenriques, your patch is in gyp itself. node-gyp copies gyp from a separate repository, stored here: https://code.google.com/p/gyp/ Please submit your issue in their repository: https://code.google.com/p/gyp/issues/list Then please come back here when your patch is integrated with gyp and we will update our code. This process takes a while because node-gyp is copied into npm and npm is copied into nodejs and gyp is also copied independently into nodejs directly, so lots of refreshes need to be made before a fix to gyp takes effect. |
It's 2014. There's still no Unicode support in |
For those who are still waiting for this to be fixed, take a look at the solution I posted here: |
I second the need for the patch. |
@MattouFP + # Fix encoding
+ xml_string = unicode(xml_string, 'latin-1').encode(encoding) is not working with cyrillic symbols 😞 + # Fix encoding for cyrillc symbols
+ xml_string = unicode(xml_string, 'Windows-1251').encode(encoding) This is not good solution in whole. Need a change solution provider maybe |
@knyazhe1, It not helps me...=( Can't install loopback: Output:
I'm from this issue #404 |
Finally fixed! My problem was in editing of the wrong file - easy_xml.py on Roaming folder (-g flag in install), but packet file runs node-gyp in Node.js installation directory. |
I believe this issue has to be re-opened. Unfortunately, the fix provided in 39a06bc affects only Western (Latin-1) releases of Windows, as Cyrillic, Greek, Turkish, Hebrew, Arabic, Baltic and Vietnamese releases use different ANSI code pages. There is, fortunately, a universal WinAPI method (available on Windows 2000 or higher) for detecting the default ANSI code page, |
@Chudesnov Could you make it into a pull request, please? As it is obvious from the existence of this issue, Nathan doesn't have required skills to support this project. Even with such a deep detail on implementation it's quite unlikely this issue will get fixed. |
Still valid. Merge #945 to fix it please |
i cant to install npm on win10. node-gyp really bad |
Problem with
.vcxproj
file. node-gyp writes it in system codepage (non-utf8), while xml prolog specifiesutf-8
inencoding
attribute. This causes error while trying to build the project.My userprofile contains cyrillic characters, so I get non-ACSII characters in paths.
The text was updated successfully, but these errors were encountered: