Basically Legacy doesn't support the spec of xoops.org
edition which has been defined after "fork". The reason is
that we can not decide Legacy's spec between JP edition and
XOOPS.org edition.
The software has to have the clear goal. Legacy's goal is
XOOPS 2.0.16 JP compatible.
Legacy's goal is XOOPS 2.0.16 JP compatible. So remember
that even if Legacy doesn't support new specs of xoops.org
edition, that's not bug.
Thank you for your response, so it is not a bug then. If
this language definition is not added to the core I think I
might just add a preload class in order to be compatible
with some XOOPS modules that use this language definition
in their comments functionality.
Sorry, we decided that Legacy 2.1 doesn't add compatibility
with xoops.org's spec after "fork", to uniform Legacy's
spec. We have to define "The Standard" of Legacy "2.1".
We will complete 2.1 on this standard, once. After that,
let's discuss what we should do. Cube is full-plugin
(full-exchangable) features. So we can test different types.
File 1: XOOPS_ROOT_PATH/language/english/comment.php
Missing: define('_CM_RE','Re');
File 2: XOOPS_ROOT_PATH/language/japanese/comment.php
Missing: define('_CM_RE','...........');
(Unfortunately my Japanese is not so good)
Solution: add missing definitions
Cheers