These directories are different encode editions of existing language directories --- japanese, korean. Now, we have to name their directory's name under extras.
When GIJOE proposed "utf encode edition" plan, its name was "japaneseutf". But, that is difficult to read correctly. Also "koreanutf" is difficult to read "korean" + "utf".
Therefore, here is new two ideas;
1) {existing language name} + "_utf8"
-> japanese_utf8
-> korean_utf8
2) {global-standard language name} + "_utf8"
-> ja_utf8
-> kr_utf8
1) is good name for existing XOOPS2 users. 2) is nice & standard naming convention for our futures.
What do you think about this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
[quote]
When GIJOE proposed "utf encode edition" plan, its name was "japaneseutf".
But, that is difficult to read correctly.
Also "koreanutf" is difficult to read "korean" + "utf".
[/quote]
japaneseutf and koreanutf !
as you mentioned, it's difficult to read correctly
but...it has some history!
I guess you can remember Nu-nrg who was active poster at jp.xoops.org!
He was forerunner of UTF-8 XOOPS!
and the very directory-name which he used for Japanese UTF-8 was "japaneseutf" .
That's one of reasons why I selected "koreanutf" as dirname of Korean UTF-8!
Umm...
I guess most of UTF-8 sites of Japan(and Korea) still use "japaneseutf"(and koreanutf) as the dirname of UTF-8 lang!
so...
I think you need to be more careful of changing its dirname!
Umm...
btw,
[quote]
1) {existing language name} + "_utf8"
-> japanese_utf8
-> korean_utf8
2) {global-standard language name} + "_utf8"
-> ja_utf8
-> kr_utf8
1) is good name for existing XOOPS2 users. 2) is nice & standard naming convention for our futures.
[/quote]
one vote for (2)!
anyway....
ko_utf8 Not kr_utf8 !!
^^;;
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you so much and please do not worry about me, wanikoo.
The naming convention named japanese+utf was thought by a lot of
cooperation of Mr. domifara.
If all the language directory names are copied from japaneseutf onto ja_utf8, it is possible to change it on the way. There is no problem at all if the user is widely notified.
I think that it is important to be going to offer UTF8 by the standard in the
future.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
sorry am i late?
how about ja_JP.UTF-8 and ko_KR.UTF-8?
these are used on the unix locales.
i think, it is easier to know language, country and character set than former method.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also I think that Legacy doesn't need to plan to handling locale rapidly, because Legacy as X2 can NOT handle locales perfectly unlike other CMS.
In addition, Legacy has local language manager class generator, it is decided from language's name. If Legacy handles locale now, we have to change Legacy much. Nobody can define the next generation spec of Legacy this week.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Plugin_Legacy will contain new two language directories;
http://sourceforge.net/forum/forum.php?thread_id=1736478&forum_id=537173
These directories are different encode editions of existing language directories --- japanese, korean. Now, we have to name their directory's name under extras.
When GIJOE proposed "utf encode edition" plan, its name was "japaneseutf". But, that is difficult to read correctly. Also "koreanutf" is difficult to read "korean" + "utf".
Therefore, here is new two ideas;
1) {existing language name} + "_utf8"
-> japanese_utf8
-> korean_utf8
2) {global-standard language name} + "_utf8"
-> ja_utf8
-> kr_utf8
1) is good name for existing XOOPS2 users. 2) is nice & standard naming convention for our futures.
What do you think about this?
[quote]
When GIJOE proposed "utf encode edition" plan, its name was "japaneseutf".
But, that is difficult to read correctly.
Also "koreanutf" is difficult to read "korean" + "utf".
[/quote]
japaneseutf and koreanutf !
as you mentioned, it's difficult to read correctly
but...it has some history!
I guess you can remember Nu-nrg who was active poster at jp.xoops.org!
He was forerunner of UTF-8 XOOPS!
and the very directory-name which he used for Japanese UTF-8 was "japaneseutf" .
That's one of reasons why I selected "koreanutf" as dirname of Korean UTF-8!
Umm...
I guess most of UTF-8 sites of Japan(and Korea) still use "japaneseutf"(and koreanutf) as the dirname of UTF-8 lang!
so...
I think you need to be more careful of changing its dirname!
Read this!
http://xoopscube.jp/modules/newbb/viewtopic.php?topic_id=7189&forum=11
Umm...
btw,
[quote]
1) {existing language name} + "_utf8"
-> japanese_utf8
-> korean_utf8
2) {global-standard language name} + "_utf8"
-> ja_utf8
-> kr_utf8
1) is good name for existing XOOPS2 users. 2) is nice & standard naming convention for our futures.
[/quote]
one vote for (2)!
anyway....
ko_utf8 Not kr_utf8 !!
^^;;
I didn't know that these names have such long history. Should we add the following option afresh.
---
3){existing language name} + "utf"
-> japaneseutf
-> koreanutf
---
> anyway....
> ko_utf8 Not kr_utf8 !!
Oops! I'm Sorry...
Hi, wanikoo and minahito.
Thank you so much and please do not worry about me, wanikoo.
The naming convention named japanese+utf was thought by a lot of
cooperation of Mr. domifara.
If all the language directory names are copied from japaneseutf onto ja_utf8, it is possible to change it on the way. There is no problem at all if the user is widely notified.
I think that it is important to be going to offer UTF8 by the standard in the
future.
We learn from the past and we should go for standards in the future
fr_utf8
it_utf8
pt_utf8
sp_utf8
as it is being adopted as a standard by almost everyone on popular open source projects.
Hi all,
Thank you for your opinions. I get to understand that we should use 2).
OK! I'll start renaming extra_languages on HEAD of Package_Legacy in CVS soon.
sorry am i late?
how about ja_JP.UTF-8 and ko_KR.UTF-8?
these are used on the unix locales.
i think, it is easier to know language, country and character set than former method.
XOOPS Cube don't have implemented handling locales. (It will be implemented in the near future.)
So Legacy don't need to implement locals soon. If Legacy implements locals, it will conflicts with XCube's locale specs in the future.
And, module developers don't agree to handle 'local' as a part of the language package, because they will have to manage too many language files.
http://www.xugj.org/modules/d3forum/index.php?post_id=2592
Also I think that Legacy doesn't need to plan to handling locale rapidly, because Legacy as X2 can NOT handle locales perfectly unlike other CMS.
In addition, Legacy has local language manager class generator, it is decided from language's name. If Legacy handles locale now, we have to change Legacy much. Nobody can define the next generation spec of Legacy this week.
to minahito-san.
OK. i probably will be propose again, if some problem happens.
thank you.