Answers.Body: <p>If it´s a one-time operation, maybe you could just import everything and search/replace in MySQL?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-24T07:13:14.513Z
Answers.LastActivityDate: 2014-09-24T07:13:14.513Z
Answers.UserDisplayName: Wolfram Gehring
Answers.Body: <p>Try enabling the config setting <a href="http://buildwithcraft.com/docs/config-settings#limitAutoSlugsToAscii" rel="nofollow"><code>limitAutoSlugsToAscii</code></a>, that should do what you want.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-22T16:33:36.080Z
Answers.Text: This works great when entering titles in the frontend, but how can I enable it on the backend? (I want to import contents from a legacy CMS via a plugin.)
Answers.UserDisplayName: Christoph Kepper
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-22T19:16:21.830Z
Answers.Text: How are you doing the import?
Answers.UserDisplayName: André Elvan
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-23T11:57:08.880Z
Answers.Text: Based on [craftimport](https://github.com/clearbold/craftimport) I created a custom input plugin where I create and save the entries.
Answers.UserDisplayName: Christoph Kepper
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-24T07:38:43.733Z
Answers.Text: I'm not sure if there is any such option serverside, but maybe you can just recreate the functionality. Check line 9311 in craft.js, the function Craft.SlugGenerator. It does basic replaces, and you can probably convert the rules easily, copying the existing regex.
Answers.UserDisplayName: Fred Carlsen
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-24T18:38:01.003Z
Answers.Text: Thank you, Fred. It's actually pretty straightforward. Craft uses a simple character map (craft.js - line 25) - I didn't know that.
Answers.UserDisplayName: Christoph Kepper
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-22T14:14:54.760Z
Answers.LastActivityDate: 2014-10-04T18:33:23.843Z
Answers.LastEditDate: 2014-10-04T18:33:23.843Z
Answers.UserDisplayName: André Elvan
Body: <p>First of all, I want to thank you for creating Craft. It's really one of the best content management systems I have ever worked with.</p>
  
  <p>I encountered an issue while working on a multilingual site: German Umlauts are not automatically transliterated (<strong>Ä -> Ae</strong>) for slugs. In other parts of Craft (e.g. field handles) Umlauts <em>are</em> transliterated automatically. </p>
  
  <p>Personally, I would prefer if this behavior could be controlled by a config variable (e.g. <code>slugExpandUmlauts</code>). </p>
  
Tags: <localization><slug>
Title: How to transform German umlauts when creating slugs?
ThreadText: # How to transform German umlauts when creating slugs?
  
  (Asked by: username_0 on 2014-09-22)
  
  First of all, I want to thank you for creating Craft. It's really one of the best content management systems I have ever worked with.
  
  I encountered an issue while working on a multilingual site: German Umlauts are not automatically transliterated (**Ä -> Ae**) for slugs. In other parts of Craft (e.g. field handles) Umlauts *are* transliterated automatically.
  
  Personally, I would prefer if this behavior could be controlled by a config variable (e.g. `slugExpandUmlauts`).
  
  **Tags:** localization, slug
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2014-09-22. Score: 4 | Accepted answer
  
  Try enabling the config setting [`limitAutoSlugsToAscii`](http://buildwithcraft.com/docs/config-settings#limitAutoSlugsToAscii), that should do what you want.
  
  > **Comments:**
  > **username_0**: This works great when entering titles in the frontend, but how can I enable it on the backend? (I want to import contents from a legacy CMS via a plugin.)  
  > **username_2**: How are you doing the import?  
  > **username_0**: Based on [craftimport](https://github.com/clearbold/craftimport) I created a custom input plugin where I create and save the entries.  
  > **username_3**: I'm not sure if there is any such option serverside, but maybe you can just recreate the functionality. Check line 9311 in craft.js, the function Craft.SlugGenerator. It does basic replaces, and you can probably convert the rules easily, copying the existing regex.  
  > **username_0**: Thank you, username_3. It's actually pretty straightforward. Craft uses a simple character map (craft.js - line 25) - I didn't know that.  
  
  ---
  
  ### Answer by username_1 on 2014-09-24. Score: -1
  
  If it´s a one-time operation, maybe you could just import everything and search/replace in MySQL?
  
  
  ---
  
  