Unicode paths results in "No such file or directory" #63853
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#63853
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello,
Operating system: Windows 10
Graphics card: Quadro M1200 + Intel HD 530 (but this is not relevant)
Blender version: 2.79b (Date: 2018-03-22, Hash:
f4dc9f9d68
)Error:
I try to open a blender file using the command line (for scripting), and the current working directory (
D:\Dev\Thèse\article
) has accents in it, which are mangled by blender. Additionally, I give it a python script for which a similar error occur. Here is what I tried on cmd:So:
Thèse
got mangled toThÞse
,result.png
, but the image is actually not saved...Seems like just a problem about unicode paths (I don't know the Blender internals though).
Added subscriber: @T.L
Added subscriber: @JacquesLucke
I could not reproduce the issue in Blender 2.79b and 2.80.
Does the same issue happen when only the .blend file has accents in its name? If yes, can you upload such a .blend file please (just to be sure, that we have the same symbol in the file name).
I just tried on another computer with Windows 10, with a file named
scène.blend
(it is just the default scene, with a simple cube). I did not use python in this second test.I put this blend file in two folder, so that on path is ascii-only, the other includes an accent (expérience):
First file
Work as intended:
Second file
Does not load:
So it seems to be only affected by accents in the folder, not in the filename.
scène.blend Here is the file with accent (but, as said, only the folder part of the path seems relevant here)
Thanks. Unfortunately, I still can't reproduce it (on Ubuntu 18.04).
Can you check if the same problem exists in Blender 2.8?
Does the same problem happen when you use Powershell?
Oh, I see, maybe there is some mismatch between utf8 on Ubuntu and utf16 on Windows/NTFS ?
Exact same behavior with Powershell. However, double-clicking the file in the file explorer works as intended.
I need to install Blender 2.8 to test, I'll keep you informed.
Added subscriber: @LazyDodo
Can't repro on 2.8 on windows
I tried with Blender 2.8, the version that I downloaded today (5 13b71c89ad0, I separated the digits to avoid another unrelated ticket !):
D:\Dev\temp>
blender scène.blend
WORKSD:\Dev\temp>
blender expérience/scène.blend
WORKSD:\Dev\temp>
blender expérience\scène.blend
WORKSD:\Dev\temp\expérience>
blender scène.blend
FAILS (Error: Cannot read fileD:\Dev\temp\expÚrience\sc├¿ne.blend
: No such file or directory)It seems to fail only if the current working directory contains non-ascii characters.
Can confirm this on windows. @JacquesLucke can you try on linux?
Added subscriber: @rjg
It's quite possible that this isn't a bug in blender, but another case of the strange way Windows handles encoding / code pages. Depending on your locale, it may be that
è
is not included in your code page, which results in Windows replacing the character with?
when passing the argument to the program. If that is the case, then there is nothing blender can do, because it's not getting the right string. You can check if that's the case by temporarily activating the UTF-8 beta feature described here. If that works properly, it's Windows' fault.Seems to be a different cause.
I'm on a french Windows, and by default my code page is 850, which includes these characters.
This seems improbable though: the arguments and the current working directory should have the same encoding (Windows-wise), but for some reason Blender only understands the arguments correctly, not the working dir...
@T.L Yes you're right, that's why I wrote that it seems to be a different cause.
I cannot reproduce it here.
Marking as confirmed, because @LazyDodo reproduced it.
This issue was referenced by
941575b1f7
Changed status from 'Open' to: 'Resolved'