Hi,

in my test terms with umlaut like "Ernährung" where not respected when terms were added to the node. Additionally I wanted to define a maximum number of 2 terms (minimum is 0) but all terms found in the node were added. I really hope that somebody can resolve this as this module is very promising - what I really like is the idea to set a maximum in order to tag just with terms which are used more often than once in the node.

Best,
Tobias

Comments

tobiberlin’s picture

tobiberlin
Primary language German
Location Berlin, Germany
commented
Title: Terms with umlaut (ä,ö,ü) and maximum number of terms not respected » Terms with umlaut (ä,ö,ü) not respected

ok... I think I made some mistakes with the settings, sorry for that - the maximum number is respected which makes this module ideal for me. But the issue with the umlauts is still there

tobiberlin’s picture

tobiberlin
Primary language German
Location Berlin, Germany
commented
Status: Active » Closed (fixed)

Ok found the error again - I use CKEditor which changes automotically from "ä" to "ä"... if anyone else has this problem as well: you can define a synonym like "Ernährung" so that the node get tagged with "Ernährung" in case that you use an WYSIWYG editor as well

AlexisWilke’s picture

AlexisWilke commented

Hi tobiberlin,

So the module is perfect after all! 8-)

With FCKeditor we could avoid the characters being transformed into &name;... I'm thinking that there is probably a similar option for CKEditor but so far I have not found it. It would be nice to know as I have problems with that when using the Geshi module (i.e. when I write code with characters such as & and ', then get transformed to & and  which is rather ugly in the output.)

That would also solve your problem with all accentuated characters.

Thank you.
Alexis Wilke

tobiberlin’s picture

tobiberlin
Primary language German
Location Berlin, Germany
commented

It is perfect, indeed :-)

For the CKEditor (http://drupal.org/project/ckeditor) you can set the entity transformation in the profile settings (advanced options). But this does just avoid entities for umlauts like ä,ö, ü. The "&" for example is still transformed into entity "&".

Best,
Tobias

AlexisWilke’s picture

AlexisWilke commented

Wow! That was easy! 8-)

Before it was in the .conf so I never thought of looking in the settings...

It is normal that the & character is always an entity and my module takes that in account, too. (There's also the < and > characters.)

Thanks much for the tip!
Alexis