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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22-6Lines changed: 22 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,13 @@
1
1
# fnorm - FixNormalization
2
2
Fix Unicode normalization in filenames.
3
3
4
+
> [!IMPORTANT]
5
+
> This software is in development. It may contains unknown or potential bugs and unexpected behaviors. If you find or encounter those, Open an issue at this repository and describe it.
6
+
4
7
## Introduction
5
-
fnorm(EEF-NOHRM) is a simple desktop application to fix Unicode normalization in filenames. From Form D to Form C, and vice versa.
8
+
**fnorm**(EEF-NOHRM) is a simple desktop application to fix Unicode normalization in filenames. From Form D to Form C, and vice versa.
6
9
7
-
It is especially useful when you met nasty messed filename including characters which can be decomposed after moving files from macOS (or Darwin based-OSes) to Windows or Linux.
10
+
It is especially useful when you met <ins>a nasty messed filename</ins> including characters which can be decomposed after moving files from macOS (or Darwin based-OSes) to Windows or Linux.
8
11
(e.g. 한글 -> 한글). In particular in Hangul, it has been considered really notorious problem among people who need to communicate files with different OSes.
9
12
10
13
This problem is derived from discrepancy in processing Unicode characters between Darwin (**macOS**, iPadOS, iOS, tvOS, watchOS, visionOS) and others, because HFS+, a filesystem that once Apple had been applied in their OSes, uses Normalization D to save filenames in UTF-16.
@@ -19,15 +22,22 @@ That's why I made this humble tool.
19
22
## Installation
20
23
21
24
```fnorm``` supports Windows, and Linux with x64 and ARM64 architectures. macOS will be supported soon.
Although the program is automatically setting console output to UTF-8, you may have to enable Windows option, '**Beta: Use Unicode UTF-8 for worldwide language support**' (Beta: 세계 언어 지원을 위해 Unicode UTF-8 사용) in Region settings to see Unicode characters correctly in Windows console environment.
34
+
That's because Windows still uses MBCS(Multi-Byte Character Set) as a default encoding in system for legacy, (e.g. CP949 for Korean) and it may causes problem in processing and showing latest Unicode characters right.
35
+
36
+
But this option can be problematic in some programs which forces or are sticked to specific encoding. (e.g. MapleStory, Fallout: New Vegas)
37
+
You can also make a workaround by type ```chcp 65001``` to set UTF-8 encoding in the console section prior to executing this program.
38
+
39
+
I recommend to run the program in Windows Terminal with PowerShell 7.
40
+
31
41
### Scoop
32
42
33
43
You can easily install fnorm in Windows with [Scoop](https://scoop.sh) and my bucket, [capella-bucket](https://github.com/Capella87/capella-bucket).
@@ -72,6 +82,10 @@ Convert filenames to follow Normalization Form C. If you don't specify ```--form
72
82
73
83
Convert filenames to follow Normalization Form D. In general cases you don't have to care about this option.
0 commit comments