mirror of
https://github.com/unshackle-dl/unshackle.git
synced 2026-11-14 13:05:09 +00:00
Deployed 34eb94b with MkDocs version: 1.6.1
This commit is contained in:
@@ -3158,10 +3158,11 @@ requires: <code>series/73871</code> for a show, <code>movies/113</code> for a fi
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>true</code></td>
|
||||
<td>Native characters preserved in filenames and folders.</td>
|
||||
<td>Native characters preserved in filenames and folders, with the vowel and tone marks of languages such as Thai, Hindi and Bengali.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>With each value, unshackle first normalises the name to Unicode NFC. A title that a service sends in composed form and in decomposed form gives the same name.</p>
|
||||
<p>Regardless of this setting, unshackle always removes or replaces a set of filesystem-unsafe and structural characters during sanitisation. For example, <code>/</code> and <code>;</code> become <code>&</code>, and unshackle removes characters like <code>\ * ! ? , ' " < > | $ # ~</code>. This is why you must never put path-unsafe characters directly in a template.</p>
|
||||
<p>unshackle warns at startup about a template that contains <code>< > : " / \ | ? *</code>. It examines a folder template per path segment, so you can use <code>/</code> there as a directory separator.</p>
|
||||
<h2 id="directory-filename-configuration">Directory & filename configuration<a class="headerlink" href="#directory-filename-configuration" title="Permanent link">¶</a></h2>
|
||||
|
||||
Reference in New Issue
Block a user