This should be "solved" by my https://trac.habariproject.org/habari-extras/browser/plugins/asciify/trunk/asciify.plugin.xml plugin. The same "problem" probably exists with tags, should also be solved with asciify.
On 13 Jan, 17:13, rick c <[email protected]> wrote: > Character set collations are a complex subject that has bitten Habari > in the past and has returned again in the form of how the umlaut is > dealt with, as noted in ticket #1359 > (https://trac.habariproject.org/habari/ticket/1359 > ). > > This issues occurs because Habari uses the utf8_unicode_ci collation > when creating MySQL tables. This collation is case insensitive, and > doesn't differentiate between characters that have an umlaut, and the > same character without the umlaut. I don't know if other accents are > affected or not. > > There isn't an issue with SQLite, which, by default, uses a binary > collation. It appears to be case sensitive, and differentiates > characters with umlauts from those without. > > My question is, would we be better off using utf8_bin for the MySQL > collation? As best I have been able to find out, it would give results > similar to what we see in SQLite when comparing strings. -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev
