Answers.Body: <p>You can pull data from entries by specifying a locale.</p>
  
  <pre><code>{% craft.entries.section('yourSection').locale('en_us') %}
  </code></pre>
  
  <p>Determine the locale you need by the custom segment. </p>
  
  <pre><code>{% set locales = {  'wetter': 'de', 'weather' : 'en_us' } %}
  {% set segment = craft.request.firstSegment() %}
  {% set entries = craft.entries.section('yourSection').locale(locales[segment]) %}
  </code></pre>
  
  <p>The big issue you will have is translating strings for each language.  If you are not at <strong>domain.com/de</strong>, I believe, you won't receive the benefits of the translation files in <em>Craft/Translations</em>. You will need to build in your own mechanism to translate strings depending on the segment.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-28T11:36:01.930Z
Answers.Text: Okay, thanks for the insight. I guess I can live with locale url segments then :)
Answers.UserDisplayName: KSPR
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-27T23:38:51.607Z
Answers.LastActivityDate: 2015-10-27T23:38:51.607Z
Answers.UserDisplayName: a-am
Body: <p>Is it possible to use craft multilanguage capabilities without <code>locale</code> url segments?</p>
  
  <p>Example:</p>
  
  <p>German: <code>domain.com/wetter</code></p>
  
  <p>English: <code>domain.com/weather</code></p>
  
  <p>I know this is pretty dangerous. If one forgets to translate the url everything will fall apart. But I wonder if it would be possible theoretically :)</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-10-26T16:40:00.953Z
Comments.Text: In your mind the German language version will live at domain.com/wetter instead of domain.com/de, In tandem the English version will live at domain.com/wether instead of domain.com/en_us?  Or are you trying to eliminate both segments and when the user changes language the url is still just domain.com?
Comments.UserDisplayName: a-am
Tags: <localization>
Title: Multilanguage without url segments
ThreadText: # Multilanguage without url segments
  
  (Asked by: username_0 on 2015-09-15)
  
  Is it possible to use craft multilanguage capabilities without `locale` url segments?
  
  Example:
  
  German: `domain.com/wetter`
  
  English: `domain.com/weather`
  
  I know this is pretty dangerous. If one forgets to translate the url everything will fall apart. But I wonder if it would be possible theoretically :)
  
  **Tags:** localization
  
  > **Comments:**
  > **username_1**: In your mind the German language version will live at domain.com/wetter instead of domain.com/de, In tandem the English version will live at domain.com/wether instead of domain.com/en_us?  Or are you trying to eliminate both segments and when the user changes language the url is still just domain.com?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-10-27. Score: 1 | Accepted answer
  
  You can pull data from entries by specifying a locale.
  
  ```
  {% craft.entries.section('yourSection').locale('en_us') %}
  
  ```
  
  Determine the locale you need by the custom segment.
  
  ```
  {% set locales = {  'wetter': 'de', 'weather' : 'en_us' } %}
  {% set segment = craft.request.firstSegment() %}
  {% set entries = craft.entries.section('yourSection').locale(locales[segment]) %}
  
  ```
  
  The big issue you will have is translating strings for each language. If you are not at **domain.com/de**, I believe, you won't receive the benefits of the translation files in *Craft/Translations*. You will need to build in your own mechanism to translate strings depending on the segment.
  
  > **Comments:**
  > **username_0**: Okay, thanks for the insight. I guess I can live with locale url segments then :)  
  
  ---
  
  