Menu
▾
▴
[xoops-svn] SF.net SVN: xoops:[9989] XoopsModules/xlanguage/trunk/xlanguage
|
From: <be...@us...> - 2012-08-05 07:11:29
|
Revision: 9989
http://xoops.svn.sourceforge.net/xoops/?rev=9989&view=rev
Author: beckmi
Date: 2012-08-05 07:11:22 +0000 (Sun, 05 Aug 2012)
Log Message:
-----------
changing file structure
Modified Paths:
--------------
XoopsModules/xlanguage/trunk/xlanguage/docs/readme.txt
Added Paths:
-----------
XoopsModules/xlanguage/trunk/xlanguage/language/tchinese_utf8/readme.tchinese.txt
Removed Paths:
-------------
XoopsModules/xlanguage/trunk/xlanguage/readme.tchinese.txt
XoopsModules/xlanguage/trunk/xlanguage/readme.txt
Modified: XoopsModules/xlanguage/trunk/xlanguage/docs/readme.txt
===================================================================
--- XoopsModules/xlanguage/trunk/xlanguage/docs/readme.txt 2012-08-05 05:08:41 UTC (rev 9988)
+++ XoopsModules/xlanguage/trunk/xlanguage/docs/readme.txt 2012-08-05 07:11:22 UTC (rev 9989)
@@ -1,34 +1,146 @@
-Read Me First
-=============
-
-Description
-------------
-The Partners module provides a page and a block for displaying links to the websites of cooperating organizations, together with short descriptions and optionally logos. Typical usage includes recognition of websites that refer a lot of traffic to your own and \x91thank you\x92 pages for sponsors.
-
- Requirements
- _____________________________________________________________________
-
-- PHP version >= 5.2.0
-- ModuleClasses in /Frameworks (download it from here: http://goo.gl/Bmknt)
-
-Install/uninstall
-------------------
-No special measures necessary, follow the standard installation process \x96 extract the xoopspartners folder into the ../modules directory. Install the module through Admin -> System Module -> Modules.
-
-Detailed instructions on installing modules are available in the XOOPS Operations Manual (http://goo.gl/adT2i)
-
-Operating instructions
-------------------------
-To set up this module you need to:
-
-i) Enter your partner\x92s details \x96 including a URL for their website and (optionally) logo plus a short description (see \x91Adding a partner\x92)
-
-ii) Configure your preferences for the module (see \x91Preferences\x92) and optionally the Partners block if you intend to use it (see \x91Blocks\x92)
-
-iii) Check that you have given your user groups the necessary module and block access rights to use this module. Group permissions are set through the Administration Menu -> System -> Groups.
-
-Detailed instructions on configuring the access rights for user groups are available in the XOOPS Operations Manual (http://goo.gl/adT2i)
-
-Tutorial
------------
-You can find a more detailed tutorial here: (http://goo.gl/ZqCFb)
\ No newline at end of file
+
+D.J.(phppp) http://xoops.org.cn
+===========================================================================================================
+
+xlanguage, eXtensible Xoops Multilingual Content and Encoding Management
+
+
+Applicable
+---------
+Any version of XOOPS and any version of any MODULE with any THEME.
+NEW in 3.02 for XOOPS 2.4.0: no hacks of api.php needed anymore
+
+
+Easy to use
+-----------
+1 All you need do is to insert ONLY ONE LINE into common.php and install "xlanguage"
+2 Do NOT need to modify/hack any other XOOPS core files or any module
+
+
+Powerful enough to meet your requirements
+-----------------------------------------
+1 Could handle as many languages of content as you want
+2 Could handle different charset of a selected language
+3 Could handle multilingual content anywhere on your site, in a module, a php file, an html page or a theme's hardcoded content
+4 Compatible with content cache
+5 Automatic detection of user browser's language preference
+
+
+User guide
+----------
+1 install "xlanguage" as a regular module
+
+2 insert one line (ONLY for XOOPS version lower than 2.4.0)
+
+ include_once XOOPS_ROOT_PATH.'/modules/xlanguage/api.php';
+ into XOOPS/include/common.php
+ RIGHT BEFORE
+ // #################### Include site-wide lang file ##################
+ if ( file_exists(XOOPS_ROOT_PATH."/language/".$xoopsConfig['language']."/global.php") ) {
+ include_once XOOPS_ROOT_PATH."/language/".$xoopsConfig['language']."/global.php";
+ } else {
+ include_once XOOPS_ROOT_PATH."/language/english/global.php";
+ }
+
+3 modify language/LocalLanguage/global.php, take "schinese" as example
+ //%%%%% LANGUAGE SPECIFIC SETTINGS %%%%%
+ //define('_CHARSET', 'GB2312');
+ //define('_LANGCODE', 'zh-CN');
+ define('_CHARSET', empty($xlanguage["charset"])?'GB2312':$xlanguage["charset"]);
+ define('_LANGCODE', empty($xlanguage["code"])?'zh-CN':$xlanguage["code"]);
+ $xlanguage['charset_base'] = "gb2312";
+
+4 select basic langauges (from an available language list) and add extended languages (upon a selected basic language) from module admin page
+ for instance, to make language switch between: English, Simplified Chinese (gb2312), Traditional Chinese (big5) and UTF-8 Chinese:
+ base 1: name: english; description(optional): English; charset: iso-8859-1; code: en (or anyother like "xen", not a true language code, just the tag for indicating English content)
+ base 2: name: schinese; description(optional): Simplified Chinese; charset: gb2312; code: zh (or anyother like "sc", not a true language code, just the tag for indicating Chinese content)
+ extended lang of schinese 1: name: tchinese; description(optional): Traditional Chinese; charset: big5 code: zh-TW (the true language code of Traditional Chinese) base: schinese
+ extended lang of schinese 2: name: utf8; description(optional): Simplified Chinese UTF-8; charset: utf-8 code: zh-CN (the true language code of Simplified Chinese) base: schinese
+
+5 make the block "langauge selection" visible
+
+6 add multilingual content with according tags sepcified for each base language (in step 4) to your modules, templates or themes[Skip this step if you do not use multi-language content display but only use charset encoding]:
+ wrap content of each language with respective tag specified in step 4:
+ [langcode1]Content of the language1[/langcode1] [langcode2]Content of the language2[/langcode2] [langcode3]Content of the language3[/langcode3] ...
+ if two or more languages have same content, you do not need add them one by one but use delimiter "|":
+ [langcode1|langcode2]Content shared by language1&2[/langcode1|langcode2] [langcode3]Content of the language3[/langcode3] ...
+ a true example (suppose the lang_codes specified in step 4 are: English-en; French-fr; SimplifiedChiense-sc):
+ [en]My XOOPS[/en][fr]Moi XOOPS[/fr][sc]\xCEҵ\xC4XOOPS[/sc]
+ OR:
+ [english|french]This is my content in English and French[/english|french][schinese]\xD6\xD0\xCE\xC4\xC4\xDA\xC8\xDD[/schinese]
+
+7 automatic conversion of content from one charset(extended language) to another [Actually on action needed in this step]
+
+8 __if__ you would like to insert hardcoded scripts for language switch in your theme or any template besides the language selection box:
+ 1) modify /modules/xlanguage/api.php "$xlanguage_theme_enable = true;"
+ 2) config options "$options = array("images", " ", 5); // display mode, delimitor, number per line";
+ 3) insert "<{$smarty.const.XLANGUAGE_SWITCH_CODE}>" into your theme or template files anywhere you prefer it present
+
+
+
+xlangauge description
+-------------------------
+An eXtensible Multi-language content and character encoding Management plugin
+Multilanguage management handles displaying contents of different languages, like English, French and Chinese
+Character encoding management handles contents of different encoding sets for one language, like GB2312 (Chinese Simplified) and BIG5 (Chinese Traditional) for Chinese.
+
+
+What xlanguage CAN do
+---------------------
+1 displaying content of specified language based on user's dynamic choice
+2 converting content from one character encoding set to another
+
+
+What xlanguage canNOT do
+------------------------
+1 xlanguage does NOT have the ability of translating content from one language to another one. You have to input contents of various languages by yourself
+2 xlanguage does NOT work without adding one line to XOOPS/include/common.php (see guide below)
+3 xlanguage does NOT have the ability of converting content from one character encoding to another if none of "iconv", "mb_string" or "xconv" is available.
+
+
+Features
+--------
+1 auto-detection of visitor's language on his first visitor
+2 memorizing users' langauge preferences
+3 switching contents of different languges/encoding sets on-fly
+4 supporting M-S-M mode for character encoding handler
+
+Note:
+M-S-M: Multiple encoding input, Single encoding storage, Multiple encoding output.
+M-S-M allows one site to fit various users with different language character encoding usages. For example, a site having xlanguage implemented porperly allows users to input content either with GB2312, with BIG5 or UTF-8 encoding and to store the content into DB with specified encoding, for say GB2312, and to display the content either with GB2312, with BIG5 or with UTF-8 encoding.
+
+
+Changelog
+---------
+xlanguage 3.02 changelog:
+1 adjusted for Xoops 2.4.0 using Preloads, no hacks of Core files required anymore in 2.4.0 and above (trabis)
+
+xlanguage 3.0 changelog:
+1 compatable for all Xoops active versions
+2 added smarty template for block
+3 added inline scripts for displaying language switch manner anywhere prefered
+
+xlanguage 2.04 changelog:
+capable for different language cache, reported by suico @ xoops.org
+
+xlanguage 2.03 changelog:
+"input" parse improvement, reported by irmtfan @ xoops.org
+
+xlanguage 2.02 bugfix for XSS vulnerability
+Thanks domifara @ dev.xoops.org
+
+xlanguage 2.01 bugfix for nonexisting language
+
+
+
+Credits
+-------
+1 Adi Chiributa - web...@ar..., language handler
+2 wjue - http://www.wjue.org, ziling BIG5-GB2312 conversion
+3 GIJOE - http://www.peak.ne.jp, easiest multilanguage hack
+
+Author
+------
+D.J. (phppp)
+http://xoops.org.cn
+http://xoopsforge.com
\ No newline at end of file
Added: XoopsModules/xlanguage/trunk/xlanguage/language/tchinese_utf8/readme.tchinese.txt
===================================================================
(Binary files differ)
Property changes on: XoopsModules/xlanguage/trunk/xlanguage/language/tchinese_utf8/readme.tchinese.txt
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Deleted: XoopsModules/xlanguage/trunk/xlanguage/readme.tchinese.txt
===================================================================
(Binary files differ)
Deleted: XoopsModules/xlanguage/trunk/xlanguage/readme.txt
===================================================================
--- XoopsModules/xlanguage/trunk/xlanguage/readme.txt 2012-08-05 05:08:41 UTC (rev 9988)
+++ XoopsModules/xlanguage/trunk/xlanguage/readme.txt 2012-08-05 07:11:22 UTC (rev 9989)
@@ -1,146 +0,0 @@
-
-D.J.(phppp) http://xoops.org.cn
-===========================================================================================================
-
-xlanguage, eXtensible Xoops Multilingual Content and Encoding Management
-
-
-Applicable
----------
-Any version of XOOPS and any version of any MODULE with any THEME.
-NEW in 3.02 for XOOPS 2.4.0: no hacks of api.php needed anymore
-
-
-Easy to use
------------
-1 All you need do is to insert ONLY ONE LINE into common.php and install "xlanguage"
-2 Do NOT need to modify/hack any other XOOPS core files or any module
-
-
-Powerful enough to meet your requirements
------------------------------------------
-1 Could handle as many languages of content as you want
-2 Could handle different charset of a selected language
-3 Could handle multilingual content anywhere on your site, in a module, a php file, an html page or a theme's hardcoded content
-4 Compatible with content cache
-5 Automatic detection of user browser's language preference
-
-
-User guide
-----------
-1 install "xlanguage" as a regular module
-
-2 insert one line (ONLY for XOOPS version lower than 2.4.0)
-
- include_once XOOPS_ROOT_PATH.'/modules/xlanguage/api.php';
- into XOOPS/include/common.php
- RIGHT BEFORE
- // #################### Include site-wide lang file ##################
- if ( file_exists(XOOPS_ROOT_PATH."/language/".$xoopsConfig['language']."/global.php") ) {
- include_once XOOPS_ROOT_PATH."/language/".$xoopsConfig['language']."/global.php";
- } else {
- include_once XOOPS_ROOT_PATH."/language/english/global.php";
- }
-
-3 modify language/LocalLanguage/global.php, take "schinese" as example
- //%%%%% LANGUAGE SPECIFIC SETTINGS %%%%%
- //define('_CHARSET', 'GB2312');
- //define('_LANGCODE', 'zh-CN');
- define('_CHARSET', empty($xlanguage["charset"])?'GB2312':$xlanguage["charset"]);
- define('_LANGCODE', empty($xlanguage["code"])?'zh-CN':$xlanguage["code"]);
- $xlanguage['charset_base'] = "gb2312";
-
-4 select basic langauges (from an available language list) and add extended languages (upon a selected basic language) from module admin page
- for instance, to make language switch between: English, Simplified Chinese (gb2312), Traditional Chinese (big5) and UTF-8 Chinese:
- base 1: name: english; description(optional): English; charset: iso-8859-1; code: en (or anyother like "xen", not a true language code, just the tag for indicating English content)
- base 2: name: schinese; description(optional): Simplified Chinese; charset: gb2312; code: zh (or anyother like "sc", not a true language code, just the tag for indicating Chinese content)
- extended lang of schinese 1: name: tchinese; description(optional): Traditional Chinese; charset: big5 code: zh-TW (the true language code of Traditional Chinese) base: schinese
- extended lang of schinese 2: name: utf8; description(optional): Simplified Chinese UTF-8; charset: utf-8 code: zh-CN (the true language code of Simplified Chinese) base: schinese
-
-5 make the block "langauge selection" visible
-
-6 add multilingual content with according tags sepcified for each base language (in step 4) to your modules, templates or themes[Skip this step if you do not use multi-language content display but only use charset encoding]:
- wrap content of each language with respective tag specified in step 4:
- [langcode1]Content of the language1[/langcode1] [langcode2]Content of the language2[/langcode2] [langcode3]Content of the language3[/langcode3] ...
- if two or more languages have same content, you do not need add them one by one but use delimiter "|":
- [langcode1|langcode2]Content shared by language1&2[/langcode1|langcode2] [langcode3]Content of the language3[/langcode3] ...
- a true example (suppose the lang_codes specified in step 4 are: English-en; French-fr; SimplifiedChiense-sc):
- [en]My XOOPS[/en][fr]Moi XOOPS[/fr][sc]\xCEҵ\xC4XOOPS[/sc]
- OR:
- [english|french]This is my content in English and French[/english|french][schinese]\xD6\xD0\xCE\xC4\xC4\xDA\xC8\xDD[/schinese]
-
-7 automatic conversion of content from one charset(extended language) to another [Actually on action needed in this step]
-
-8 __if__ you would like to insert hardcoded scripts for language switch in your theme or any template besides the language selection box:
- 1) modify /modules/xlanguage/api.php "$xlanguage_theme_enable = true;"
- 2) config options "$options = array("images", " ", 5); // display mode, delimitor, number per line";
- 3) insert "<{$smarty.const.XLANGUAGE_SWITCH_CODE}>" into your theme or template files anywhere you prefer it present
-
-
-
-xlangauge description
--------------------------
-An eXtensible Multi-language content and character encoding Management plugin
-Multilanguage management handles displaying contents of different languages, like English, French and Chinese
-Character encoding management handles contents of different encoding sets for one language, like GB2312 (Chinese Simplified) and BIG5 (Chinese Traditional) for Chinese.
-
-
-What xlanguage CAN do
----------------------
-1 displaying content of specified language based on user's dynamic choice
-2 converting content from one character encoding set to another
-
-
-What xlanguage canNOT do
-------------------------
-1 xlanguage does NOT have the ability of translating content from one language to another one. You have to input contents of various languages by yourself
-2 xlanguage does NOT work without adding one line to XOOPS/include/common.php (see guide below)
-3 xlanguage does NOT have the ability of converting content from one character encoding to another if none of "iconv", "mb_string" or "xconv" is available.
-
-
-Features
---------
-1 auto-detection of visitor's language on his first visitor
-2 memorizing users' langauge preferences
-3 switching contents of different languges/encoding sets on-fly
-4 supporting M-S-M mode for character encoding handler
-
-Note:
-M-S-M: Multiple encoding input, Single encoding storage, Multiple encoding output.
-M-S-M allows one site to fit various users with different language character encoding usages. For example, a site having xlanguage implemented porperly allows users to input content either with GB2312, with BIG5 or UTF-8 encoding and to store the content into DB with specified encoding, for say GB2312, and to display the content either with GB2312, with BIG5 or with UTF-8 encoding.
-
-
-Changelog
----------
-xlanguage 3.02 changelog:
-1 adjusted for Xoops 2.4.0 using Preloads, no hacks of Core files required anymore in 2.4.0 and above (trabis)
-
-xlanguage 3.0 changelog:
-1 compatable for all Xoops active versions
-2 added smarty template for block
-3 added inline scripts for displaying language switch manner anywhere prefered
-
-xlanguage 2.04 changelog:
-capable for different language cache, reported by suico @ xoops.org
-
-xlanguage 2.03 changelog:
-"input" parse improvement, reported by irmtfan @ xoops.org
-
-xlanguage 2.02 bugfix for XSS vulnerability
-Thanks domifara @ dev.xoops.org
-
-xlanguage 2.01 bugfix for nonexisting language
-
-
-
-Credits
--------
-1 Adi Chiributa - web...@ar..., language handler
-2 wjue - http://www.wjue.org, ziling BIG5-GB2312 conversion
-3 GIJOE - http://www.peak.ne.jp, easiest multilanguage hack
-
-Author
-------
-D.J. (phppp)
-http://xoops.org.cn
-http://xoopsforge.com
\ No newline at end of file
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
