@ghia

So the user overwrites the contents of:

modules/indexscan/language/nederlands/

with content from either:

utf/modules/indexscan/language/nederlands/
or
iso/modules/indexscan/language/nederlands/

?

(not sure I get this...)

harden in UTF-8=japanese folder,
but want to look at the state a little more just to make sure.

Quote:
"XOOPS.me" is my XOOPS site.
I am suspended to update it to XOOPS 2.4,
I cannot show a site unless this story is made up.

When I make XOOPS Japan site, I register a different domain.

@sailjapan:
That's right!

As the original (default) modules/indexscan/language/nederlands/ is the UTF-8 version, the user can 'fallback' to the ISO (ansi) encoding by copying the contents of the iso directory.
Traditionally, all Dutch sites used a latin1 database and ISO-8859-1(5) encoding.

Strictly, the utf directory is not necessary, but it is supplied for convenience, eg. for easy resetting a previous iso copy operation.
Or for future upgrading, eg. when the database can reliable converted from latin (=ISO site) to utf.

As it is more or less imperatif (to have the least problems), that the encoding of your site goes with the encoding of your database, I don't think it is a good idea to offer the user the choice between eg japanese-EUC or japanese-UTF
IMHO it is best to always start from the database encoding and have the sites' encoding along.

Existing sites which have EUC encoding in their database, should have also the same encoding for the site, with parameters for charset in accordance in mainfile.php and global.php

New sites are advised to have full utf (database and files). One problem here, is that most older module translations are done with (and contain thus only) the ISO (ansi) files. The user has to convert them, with NotePad++ to UTF-8 without BOM.

ghia, Thank you for a careful answer.

Quote:
CMS compatible with XOOPS continues still showing it in EUC.
(seem to make it UTF-8 in the next version)
While there is little it,
the Japanese module exhibition must examine a public method according to the language...

I generated a project in Google Code to be able to update it more easily.

https://code.google.com/p/xoops-japanese/

I showed a test version with specifications of UTF-8=japanese folder now.

And, the access to SourceForge.net had permission.
I made folder 2.4.5 and confirmed it. (ID: ROUTE286)

I throb to big one step!

Excellent progress, 2-8-6 san! Thanks for sharing

Reflected to SourceForge.net before I upload it...


I revise it until a while ago and update XOOPS 2.4.5 test version:

https://code.google.com/p/xoops-japanese/

Except Syntax Error, the Japanese reason is quite completed.

it's here http://xoopscube.jp/forum/6684