Dear Magnolians
I think this was a topic some time ago and I assumed it wouldn't bite
me again. But it did:
When entering content (both in mag. 3.6.8 and 4.1.1 CE) through FCK
with default config (magnoliaStandard.js) all umlaut characters get
translated into their html encoding (ie. ä -> &auuml; and so on).
This unfortunately leads to the situation that simple search cannot
find the content anymore (ie searching for Zürich does not find
Zürich, obviously).
Now you could argue why not encode search string -> it wouldn't find
titles (and other content entered with normal edit) anymore as well as
trash the searchResultSnippet output.
Of course I can go and copy the content of /.resources/fckeditor/
custom/config/magnoliaStandard.js add FCKConfig.IncludeLatinEntities =
false; and point through jsConfigFile to my custom .js (which I did
for the current running projects).
But I think this is just a brittle hack and most certainly will haunt
me one day.
So my questions are:
a. is the encoding of the content intentional?
b. if so is there a more elegant way to accomplish the same behaviour,
ie not encoding my umlauts?
c. what about making it configurable same way as
images,tables,fontSizes and such?
Any feedback is much appreciated.
cheers to all, Thomas
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
