Timeline for UTF8 Character Makes File Inaccessible
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 16, 2019 at 19:31 | vote | accept | user3783243 | ||
| Jan 16, 2019 at 19:25 | comment | added | DrYak | Nope, your Mac betrayed you that you're a Mac user, and that's where the whole thing stems from. 'ö' and 'ö' just aren't the same Unicode codepoint and that's something that Linux conserves (just like it's also case sensitive). | |
| Jan 16, 2019 at 19:23 | answer | added | DrYak | timeline score: 4 | |
| Jan 16, 2019 at 18:28 | comment | added | DrYak |
Damn, same locale... - does using rsync instead of scp also barf on that file ?
|
|
| Jan 16, 2019 at 18:00 | comment | added | user3783243 | @DrYak I've updated the question with that info, both look the same to me. | |
| Jan 16, 2019 at 17:59 | history | edited | user3783243 | CC BY-SA 4.0 |
add locale information
|
| Jan 16, 2019 at 17:54 | comment | added | DrYak |
What's the locale running on both instances ? (Type locale) This type of problems might happen when both side don't use the same locale (preferably a .UTF-8 ending one).
|
|
| Jan 16, 2019 at 16:52 | history | asked | user3783243 | CC BY-SA 4.0 |