Item13497: Group topic not detected as WikiWord
Priority: Normal
Current State: Closed
Released In: 2.1.0
Target Release: minor
Applies To: Engine
Component: I18N, Unicode
Branches:
Repo (at least on OS X)
- Create a GROUP
ÚňíGroup
- to some topic add %GROUPINFO{format="Main.$name"}%
The result is like the following, e.g. unusable.
* screenshot_94.png:

In the
WikiGroups (and the OLD GROUPS macro) is OK.
* screenshot_93.png:

--
JozefMojzis - 03 Jul 2015
This could be again only Normalisation problem... don't know - need test on Linux or such.
--
JozefMojzis - 03 Jul 2015
Looks OK to me....
ÚňíGroup
--
Main.CrawfordCurrie - 03 Jul 2015 - 11:17
The
ÚňíGroup (in the Sandbox) work for me too. This is about the
WikiGroups, or if you want exactly about the
%GROUPINFO% macro what *doesn't works ok, at least on OS X Did you read the content of the Task?

or
--
JozefMojzis - 03 Jul 2015
I added
ÚňíGroup on trunk. Other than sorting wrong,
ÚňíGroup shows up in both the
AdminGroup,
BaseGroup,
AMStudyGroup,
AntiWikiSpamBypassGroup,
AssociationBoardGroup,
BlogAuthorGroup, Main.CDBCGroup,
ConsistGroup,
ContentMigrationGroup,
CoreDevelopersGroup,
DevelopersGroup,
DocumentationGroup,
ExtensionDevelopersGroup,
InfrastructureTaskTeamGroup,
MaintainGroup,
NanoLundTritonGroup,
NewNameGroup,
NobodyGroup,
ReleaseManagersGroup, Main.SQIM-Test_Group,
SecurityGroup and on the
http://trunk.foswiki.org/Main/WikiGroups topic. Must be OSX specific?
--
GeorgeClark - 03 Jul 2015
ok, so confirmend - again one normalisation problem. thank you
Temporary fix, util the core solve it:
--- Foswiki-2.0.0-RC2orig/lib/Foswiki/Macros/GROUPINFO.pm 2015-07-01 16:27:37.000000000 +0200
+++ Foswiki-2.0.0-RC2/lib/Foswiki/Macros/GROUPINFO.pm 2015-07-03 14:14:46.000000000 +0200
@@ -3,6 +3,7 @@
use strict;
use warnings;
+use Unicode::Normalize;
BEGIN {
if ( $Foswiki::cfg{UseLocale} ) {
@@ -136,6 +137,7 @@
}
else {
$result = $header . join( $sep, @rows ) . $footer;
+ $result = NFC($result) if $Foswiki::UNICODE;
}
return expandStandardEscapes($result);
}
--
JozefMojzis - 03 Jul 2015
I believe that this should have been fixed in 2.1.0 where we added normalization by default. Setting to closed.
--
GeorgeClark - 25 Sep 2016