<p>Intention: create a local <code>Asset Volume</code> with a bunch of subfolders and files in it and display a file tree on frontend.</p>
<p>All OK, but since the website is in German, I have to do <code>'convertFilenamesToAscii' =&gt; true</code> but this setting also affects folder names. So all the non-Latin letters are transliterated and we can not use it in the front-end.</p>
<p>I see that <code>models/VolumeFolder</code> has got <code>$name</code> and <code>$path</code> properties and in theory it looks like it would be possible to transliterate <code>$path</code>, but keep <code>$name</code> as is. In the real world, though, as I see it, I would have to extend quite some core classes to make it work.</p>
<p>Maybe someone has got a better idea how to keep folder names with all the non-Latin chars and use ASCII paths?</p>

CC BY-SA 4.0
2021-12-14T12:42:20.600Z
Or maybe I should just turn the ascii conversion off? I'm used to keeping things safe, but when google says it's OK, then maybe I should not worry? https://searchengineland.com/google-using-non-english-urls-non-english-websites-fine-294758
anvar
CC BY-SA 4.0
2021-12-16T16:48:15.203Z
But still, even with `convertFilenamesToAscii = false`, there's a problem with special characters (I'd need at least spaces in names).
anvar
<assets><control-panel><subfolder>
Local Volume Folder: Transliterate path, but keep name as is
# Local Volume Folder: Transliterate path, but keep name as is

(Asked by: username_0 on 2021-12-14)

Intention: create a local `Asset Volume` with a bunch of subfolders and files in it and display a file tree on frontend.

All OK, but since the website is in German, I have to do `'convertFilenamesToAscii' => true` but this setting also affects folder names. So all the non-Latin letters are transliterated and we can not use it in the front-end.

I see that `models/VolumeFolder` has got `$name` and `$path` properties and in theory it looks like it would be possible to transliterate `$path`, but keep `$name` as is. In the real world, though, as I see it, I would have to extend quite some core classes to make it work.

Maybe someone has got a better idea how to keep folder names with all the non-Latin chars and use ASCII paths?

**Tags:** assets, control-panel, subfolder

> **Comments:**
> **username_0**: Or maybe I should just turn the ascii conversion off? I'm used to keeping things safe, but when google says it's OK, then maybe I should not worry? https://searchengineland.com/google-using-non-english-urls-non-english-websites-fine-294758  
> **username_0**: But still, even with `convertFilenamesToAscii = false`, there's a problem with special characters (I'd need at least spaces in names).  

---

## 0 answers

