11
KeiichiSHIGA
Mention of the country is not enough on a Xoops Language (language/XXX/countries.php)

When I worked on the Japanization,
I noticed that mention of the country was insufficient of XOOPS Language
(language/XXX/countries.php):

Jersey (ISO 3166: JE)

There is file countries.php with XOOPS 2.4/2.5.

Reference: Wikipedia - ISO 3166-1



12
KeiichiSHIGA
Re: XOOPS 2.4.x Translations

I show a Japanese language file experimentally as topic of this place

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

There was not inconvenience and reflects it to SourceForge.net.



13
KeiichiSHIGA
Re: Japanese Translations (XOOPS 2.5)

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!



14
KeiichiSHIGA
Re: Japanese Translations (XOOPS 2.5)

ghia, Thank you for a careful answer.

Quote:

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.

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...



15
KeiichiSHIGA
Re: Japanese Translations (XOOPS 2.5)

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

Quote:
- xoops.me?

"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.



16
KeiichiSHIGA
Re: Japanese Translations (XOOPS 2.5)

I begin to think it to have possibilities to be good by structure adopting by other languages.
In other words the UTF-8 and EUC a japanese folder.

When we did it in this way,

The module which was shown in ja_utf8 conventionally:
The person changes a folder name in japanese.

The module which was shown in EUC:
The person converts a language file into UTF-8.

Many modules do not become the big trouble that this work complies with.

I regard the trouble of the result to display as "ja_utf8" in a list of languages.
I think that this must assume it "japanese".


To sailjapan:
My acquaintance manages the domain called "xoops.jp" now.
(I transferred it to the person after I owned it before)
But the person is not active in XOOPS Japan support.
Please do not use this notation to avoid confusion.
I intend to install XOOPS Japan support in another domain.



17
KeiichiSHIGA
Re: Japanese Translations (XOOPS 2.5)

I watched the language file of the other language. As a result, folder is 1.
In fact, at this point I am troubled once when I make a language file of XOOPS 2.4.4.

trouble of the module installation (now) to make UTF-8 with a japanese folder.
However, I think that it is necessary to display "japanese" by the choice of the language.
I want an opinion of all of you in this respect.



18
KeiichiSHIGA
Re: Japanese Translations (XOOPS 2.5)

Quote:
Has anyone at xoops.jp translated (EUC or UTF) XOOPS 2.3.x or 2.4.x or 2.5 language files yet? I don't want to duplicate work.

I am testing the Japanese language file of XOOPS 2.4.4.
(I was going to show it in XOOPS.me in few days.)
If even this is good, I offer it.



19
KeiichiSHIGA
Re: Japanese Translations (XOOPS 2.5)

deka87, Thank you for good support.
Of course even other languages will have the same problem.

Quote:

i used this script to convert my whole database to utf-8 from cp-1251. all you need is to upload it to the website root and run. it was created for russian websites in particular, but i think if you know php you can easily modify it to convert a database from latin to utf-8.

for more info you can address to this thread.


If this is upgrading work of XOOPS or the module of the simple substance, the beginner who is not good at PHP works.

XOOPS 2.0 were considerably adopted in Japan.
(Because the person who developed XOOPS is a Japanese)
Please understand that there is not little one that is not good at operation of PHP and MySQL in that.

There is a big problem one more in this respect.
MySQL 4.1-5.0 had a problem for Japanese handling.
Therefore it is that there is a lot still a japanese server managed in MySQL 4.0.



20
KeiichiSHIGA
Re: Japanese Translations (XOOPS 2.5)

As for the XOOPS (Compatible CMS) modules of the Japanese product,
development is continued in this custom now.
(this custom: japanese = EUC / ja_utf8 = UTF-8 )

It will disturb this custom to generate japanese folder in UTF-8.
This is that trouble to revise a language file by manual labor for much XOOPS modules occurs.




TopTop
« 1 (2) 3 »



Login

Who's Online

126 user(s) are online (78 user(s) are browsing Support Forums)


Members: 0


Guests: 126


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits