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

Processing/GRASS don't work under Windows if username or input/output paths have non ascii chars #20770

Closed
qgib opened this issue Apr 27, 2015 · 10 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! GRASS

Comments

@qgib
Copy link
Contributor

qgib commented Apr 27, 2015

Author Name: Giovanni Manghi (@gioman)
Original Redmine Issue: 12657
Affected QGIS version: 3.4.4
Redmine category:processing/grass
Assignee: Victor Olaya


Already discussed with Victor and Alexander. The issue has no easy solution apparently.

If the username has non ascii chars in it Processing returns the error message saying that GRASS is not installed.

If the non ascii chars are in the input/output paths then the modules run but ultimately fail.

This is no issue under Linux.


Related issue(s): #18019 (relates), #21185 (relates), #24160 (relates)
Redmine related issue(s): 9425, 13120, 16250


@qgib
Copy link
Contributor Author

qgib commented Jun 1, 2015

Author Name: Giovanni Manghi (@gioman)


  • version was changed from 2.8.1 to master
  • priority_id was changed from Normal to High
  • fixed_version_id was configured as Future Release - High Priority

@qgib
Copy link
Contributor Author

qgib commented Mar 5, 2016

Author Name: Médéric RIBREUX (Médéric RIBREUX)


Hello,

I am working on it (only made with GRASS7)...

Following my work on #18019, I found a way to use input and output files with mbcs characters in their name for GRASS7 algorithms.

I have made the fix tests on MS-Windows XP for the moment (the only VM with MS I have). I will try it on MS-Windows 7 next week and make a Pull-Request for this soon (so you can test it).

Stay tuned !


  • status_id was changed from Open to In Progress

@qgib
Copy link
Contributor Author

qgib commented Mar 5, 2016

Author Name: Giovanni Manghi (@gioman)


thanks!

@qgib
Copy link
Contributor Author

qgib commented Mar 7, 2016

Author Name: Médéric RIBREUX (Médéric RIBREUX)


Hello,

the "PR is published":#2882.

Feel free to test it !

@qgib
Copy link
Contributor Author

qgib commented Jan 4, 2017

Author Name: Giovanni Manghi (@gioman)


  • pull_request_patch_supplied was changed from 0 to 1

@qgib
Copy link
Contributor Author

qgib commented Mar 7, 2017

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id removed Future Release - High Priority
  • priority_id was changed from High to Normal
  • status_id was changed from In Progress to Open

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • easy_fix was configured as 0
  • regression was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Jan 25, 2019

Author Name: Victor Olaya (@volaya)


Things seem to be fine in 3.4.

Should this be closed?


  • description was changed from Already discussed with Victor and Alexander. The issue has no easy solution apparently.

If the username has non ascii chars in it Processing returns the error message saying that GRASS is not installed.

If the non ascii chars are in the input/output paths then the modules run but ultimately fail.

This is no issue under Linux. to Already discussed with Victor and Alexander. The issue has no easy solution apparently.

If the username has non ascii chars in it Processing returns the error message saying that GRASS is not installed.

If the non ascii chars are in the input/output paths then the modules run but ultimately fail.

This is no issue under Linux.

  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Jan 25, 2019

Author Name: Giovanni Manghi (@gioman)


Victor Olaya wrote:

Things seem to be fine in 3.4.

Should this be closed?

I will check ASAP.

@qgib
Copy link
Contributor Author

qgib commented Jan 28, 2019

Author Name: Giovanni Manghi (@gioman)


yes, it seems fixed!


  • resolution was changed from to fixed/implemented
  • pull_request_patch_supplied was changed from 1 to 0
  • status_id was changed from Feedback to Closed
  • version was changed from master to 3.4.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! GRASS
Projects
None yet
Development

No branches or pull requests

1 participant