Available in other languages:
中文版本 ｜ 日本語版
When working across different development environments,
file formats can easily become inconsistent — especially with text encodings and line endings.
This repository provides a sample Unity tool
for automatically unifying those formats across your project.
You’re encouraged to modify and adapt the implementation
to fit your own workflow or project needs.
That said, using proper configuration tools such as .editorconfig
is still highly recommended to prevent such inconsistencies in the first place.
This project uses ReadJEnc,
a pure C# library for character encoding detection and conversion.
Since Unity does not directly support NuGet,
you’ll first need to install NuGetForUnity.
- Install NuGetForUnity in your project.
- Open NuGet > Manage NuGet Packages from the Unity menu.
- Search for ReadJEnc and install it.
The ReadJEnc library is compiled into a DLL file named Hnx8.ReadJEnc.
If your project uses assembly definitions, make sure to explicitly add a reference to this DLL.
After installing ReadJEnc, download the latest Unity package from the
latest Release page
and import it into your project.
Once compilation is complete, you can open the tool from
Tools > Scripts Validator (Open Window) in the Unity Editor.
Note:
ReadJEnc is particularly effective at detecting file encodings that include Japanese text.
Depending on the primary language used in your project,
you may not need this library — or you might prefer to replace it with a different one.Also, ReadJEnc is an external library maintained by a third party.
Please review its license and terms of use before including it in your project.
Before running the conversion, specify two things:
the root directory (the folder to search recursively)
and the target file extensions.
Currently supported extensions are:
.cs, .shader, .hlsl, .txt, and .md.
Next, select the desired destination encoding and line ending format,
then click Run Conversion.
Since this operation is irreversible,
a confirmation dialog will appear before execution.
As mentioned earlier, this tool is provided as a sample implementation,
so feel free to modify it to suit your project’s workflow.
For large-scale projects with a massive number of scripts,
you may want to extend the search paths beyond just the Assets/ directory.
The tool processes each detected file sequentially:
it converts files that require changes,
skips any that encounter errors,
and logs detailed information for every processed file —
making it easy to review exactly what was modified.
This repository is released under the MIT License.
See the LICENSE file for details.