Item12945: Words starting Uppercase and have an umlaut will render to garbage like looking wikiwords.
Priority: Normal
Current State: Closed
Released In: 2.0.0
Target Release: major
Summary
Because
CharsetConverterContrib was released, i thought that Utf8 would be the right way to go.
However the following happens:
- Any word that starts uppercase and contains an umlaut renders to a "garbage" wikiword. So it is not a wikiword but the engine tries to render it as such.
- If the same word starts lowercase, it renders correctly.
- Editing using the tml editor shows the correct word.
Example
nachfolgende Bl��cke auswirken
nachfolgende blöcke auswirken
Live using this Web (seems to work here)
nachfolgende blöcke auswirken
nachfolgende Blöcke auswirken.
It also happens quite often, that when saving using the Wysiwyg/Tml editor, text get "garbage" characters.
I will open a seperate task for this, but thought it might be worth mentioning.
Edit: Task opened:
Item12946
Example:
%STARTSECTION{"searchbytopic"}%
<div class="jqDataTablesContainer {'bFilter':true, 'bPaginate':true, 'bInfo':true }">
%SEARCH{
  "1"
  type="query"
  topic="*"
  header="| *Name* | *Date* | *Author* |"
  format="| $topic | $date | $wikiname |"
  nonoise="on"
}%
</div>
%ENDSECTION{"searchbytopic"}%
Settings
- {UserInterfaceInternationalisation} On
- {UseLocale} On
- {Site}{Locale} de_DE.utf8
- {Site}{CharSet} utf-8
Linux locales:
root# locale -a
C
C.UTF-8
de_AT.utf8
de_BE.utf8
de_CH.utf8
de_DE
de_DE.iso88591
de_DE.utf8
de_LI.utf8
de_LU.utf8
en_AG
en_AG.utf8
en_AU.utf8
en_BW.utf8
en_CA.utf8
en_DK.utf8
en_GB.utf8
en_HK.utf8
en_IE.utf8
en_IN
en_IN.utf8
en_NG
en_NG.utf8
en_NZ.utf8
en_PH.utf8
en_SG.utf8
en_US.utf8
en_ZA.utf8
en_ZM
en_ZM.utf8
en_ZW.utf8
POSIX
--
WolfgangAlper - 20 Jun 2014
Jast, Crawford, can either of you confirm the
WikiWord rendering part of this. The Edit issues are fixed. Is this related to use of Locales?
--
GeorgeClark - 23 Dec 2014
Looks OK to me.
--
CrawfordCurrie - 09 Feb 2015