Answers.Body: <p>If you have a global set named <em>globalSet</em>, and a plain text field in that set named <em>textField</em>, and the value you enter is <em>Eng</em>, then <code>{{globalSet.textField}}</code> will output <em>Eng</em></p>
  
  <p>Things that could be going wrong:</p>
  
  <ul>
  <li>caps-lock: Did you enter <em>ENG</em> in the field in the first place?</li>
  <li><em>|upper</em>: <code>{{globalSet.textField|upper}}</code> will output <em>ENG</em></li>
  <li>CSS: <code>text-transform: uppercase;</code></li>
  <li>jQuery: <code>$("*").text($("*").text().toUpperCase());</code> (or other jQuery)</li>
  <li>all caps font</li>
  <li>translations: <code>{{globalSet.textField|t}}</code> and a translation file with <code>"Eng" =&gt; "ENG"</code></li>
  </ul>
  
  <p>[edited to fold in suggestions from the coments - Marion]</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-03T06:51:47.887Z
Answers.Text: Another thing that could be going wrong, CSS. ;) Double check for `text-transform: uppercase`.
Answers.UserDisplayName: Simon Kuran
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-03T07:00:37.897Z
Answers.Text: Yeah, and also double check for jQuery `$("*").text($("*").text().toUpperCase());`
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-03T07:13:00.683Z
Answers.Text: One more: you could be using an "All caps font"?!
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-03T07:14:24.997Z
Answers.Text: What could also cause this is translations. `{{globalSet.textField|t}}` and a translation file with `"Eng" => "ENG"`!
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-03T07:17:26.327Z
Answers.Text: Go into your global and copy it to the clipboard, then open up Microsoft word and paste it in the contents of your global field into a new document. Highlight the text you want to be lowercase and select the 'Aa' button and select "Capitalize each word". The text is now changed into the format your template requires. Place this text back into your global and click save. 
  
  I have taken the time to ensure my instructions are clear by taking a screenshot of the Microsoft Word menu item: http://glui.me/?i=gsxz5xohmgyq8av/2014-07-03_at_3.15_pm.png/
  
  Please let me know if you need further assistance
Answers.UserDisplayName: Luke Holder
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-03T07:32:27.823Z
Answers.Text: @Luke this is a very nice tutorial, good work, but why didn't you make it a dedicated answer?!
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-03T07:34:37.073Z
Answers.Text: @ChristianSeelbach i'm working on a more detailed answer and hope to release a beta in a few weeks.
Answers.UserDisplayName: Luke Holder
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-03T07:35:29.683Z
Answers.Text: @Moin please keep in mind, that if you are following Luke's tutorial you still could encounter problems with error options 2, 3, 4, 5 or 6!
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-03T05:48:42.127Z
Answers.LastActivityDate: 2014-07-03T18:08:26.557Z
Answers.LastEditDate: 2014-07-03T18:08:26.557Z
Answers.UserDisplayName: Marion Newlevant
Body: <p>My question is simple and straightforward. Maybe I am making a mistake but it seems that all the text in a global field is always capital. I want to have 'Eng" in a global plain text field but it outputs "ENG"</p>
  
Tags: <templating>
Title: Is it possible to have lowercase globals?
ThreadText: # Is it possible to have lowercase globals?
  
  (Asked by: username_0 on 2014-07-03)
  
  My question is simple and straightforward. Maybe I am making a mistake but it seems that all the text in a global field is always capital. I want to have 'Eng" in a global plain text field but it outputs "ENG"
  
  **Tags:** templating
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-07-03. Score: 5
  
  If you have a global set named *globalSet*, and a plain text field in that set named *textField*, and the value you enter is *Eng*, then `{{globalSet.textField}}` will output *Eng*
  
  Things that could be going wrong:
  
  * caps-lock: Did you enter *ENG* in the field in the first place?
  * *|upper*: `{{globalSet.textField|upper}}` will output *ENG*
  * CSS: `text-transform: uppercase;`
  * jQuery: `$("*").text($("*").text().toUpperCase());` (or other jQuery)
  * all caps font
  * translations: `{{globalSet.textField|t}}` and a translation file with `"Eng" => "ENG"`
  
  [edited to fold in suggestions from the coments - username_1]
  
  > **Comments:**
  > **username_2**: Another thing that could be going wrong, CSS. ;) Double check for `text-transform: uppercase`.  
  > **username_3**: Yeah, and also double check for jQuery `$("*").text($("*").text().toUpperCase());`  
  > **username_3**: One more: you could be using an "All caps font"?!  
  > **username_3**: What could also cause this is translations. `{{globalSet.textField|t}}` and a translation file with `"Eng" => "ENG"`!  
  > **username_4**: Go into your global and copy it to the clipboard, then open up Microsoft word and paste it in the contents of your global field into a new document. Highlight the text you want to be lowercase and select the 'Aa' button and select "Capitalize each word". The text is now changed into the format your template requires. Place this text back into your global and click save.   I have taken the time to ensure my instructions are clear by taking a screenshot of the Microsoft Word menu item: http://glui.me/?i=gsxz5xohmgyq8av/2014-07-03_at_3.15_pm.png/  Please let me know if you need further assistance  
  > **username_3**: @username_4 this is a very nice tutorial, good work, but why didn't you make it a dedicated answer?!  
  > **username_4**: @ChristianSeelbach i'm working on a more detailed answer and hope to release a beta in a few weeks.  
  > **username_3**: @username_0 please keep in mind, that if you are following username_4's tutorial you still could encounter problems with error options 2, 3, 4, 5 or 6!  
  
  ---
  
  