Handling Unicode Normalization of Filenames in Next.js
Unanswered
West African Crocodile posted this in #help-forum
West African CrocodileOP
I have encountered an issue while using Next.js to handle images with Japanese filenames, where files cannot be correctly loaded due to differences in Unicode normalization.
Specifically, filenames that appear identical, such as "クーリングタワー.svg", are treated as different strings internally. One uses the composed character "グ" (U+30B0), while the other uses the decomposed characters "ク" (U+30AF) and the combining dakuten "゙" (U+3099).
Due to this difference, attempting to load the file results in an error stating that the file does not exist.
It would be extremely helpful if Next.js could provide functionality to automatically perform Unicode normalization (e.g., normalization to NFC) on filenames.
Could you please advise me on where I should officially submit this feature request?
Specifically, filenames that appear identical, such as "クーリングタワー.svg", are treated as different strings internally. One uses the composed character "グ" (U+30B0), while the other uses the decomposed characters "ク" (U+30AF) and the combining dakuten "゙" (U+3099).
Due to this difference, attempting to load the file results in an error stating that the file does not exist.
It would be extremely helpful if Next.js could provide functionality to automatically perform Unicode normalization (e.g., normalization to NFC) on filenames.
Could you please advise me on where I should officially submit this feature request?