Handling precomposed and decomposed filename formatting

Hello.

I've noticed something and, whilst not necessarily a SilverBullet specific "issue" or anything, I wanted to write about it here to see if others have encountered my problem and if there's a good "SilverBullet-only" way for me to get around it.

Setup and problem: I have silverbullet on my android phone (running iodeos specifically) and mac, and I sync my space with syncthing. If I create files with names including multi-glyph characters like á or ö, then many SilverBullet functionalities behave badly while syncthing syncs my space (I presume because the filenames themselves are swapping between precomposed and decomposed formatting). For example, string.byte on the filenames returned from queries will not consistently output the same result and referencing files with [[...]] will not consistently work over time. To be clear, the files themselves are not duplicated and content is never lost, but things like the linked mentions section of a file are inconsistent over time and between devices.

I've seen that similar problems are very commonly talked about in the syncthing community (eg: Cross platform: character sets and filename limitations - #5 by calmh - Development - Syncthing Community Forum), and I can imagine many different fixes for this that target different software in the overall chain of things that ultimately cause the problem.

Out of interest though: has anyone encountered a similar issue and has found a clean SilverBullet-only workaround? Has anyone tried to customise SilverBullet to normalize both the indexed page names and the parsed link targets before comparing them, so on-disk encoding stops mattering entirely?

Thanks :))