xLanguage (Wordpress Plugin)
Monday, January 21st, 2008目錄
|Contents
同類比較
Comparisons
Compare to qTranslate v2.0.2 (Jan 2009)
The logic behind qTranslate is similar to that of xLanguage – both using HTML tag to differentiate the contents of languages and requires no database modification. qTranslate uses HTML comment tag while xLanguage uses the lang=”..” attribute.
The major differences lie within the admin interface, qTranslate provides strong Admin UI integration such that user enters the title, the category name and so on in independent textbox. The post is also to be post to an independent editor. While xLanguage, user enters the data in the same input box. For authoring in language that are very similar (like Cantonese and Written Chinese), and that cross-authoring is common, the method that xLanguage use will reduce much duplication work.
Due to the above restriction, qTranslate supports only one-to-one mapping between authoring and viewable lanugage. while xLanguage does not have this restriction. And hence, xLanguage allows all texts to be presented under one single URL for search engine to crawl with. (Think of SEO)
Feature-wise, xLanguage currently lacks of Pre-domain URL Permalinks mode, as well as automatic MO file download. (Note: MO does work in xLanguage but just have to be downloaded manually). Contribution would certainly help in accelerate these getting done 
.
Compare to Gengo v2.5.3 (Jan 2009)
Gengo v2.5.3 is not tested with Wordpress 2.7 according to the published plugin info.
In Gengo, each translations is a standalone post, linked to the original post. It enables you to create maps between different content. Think of different language version of Wikipedia, basically Gengo is the same – and it helps you to maintain such link table.
In xLanguage, everything is in the same post. The xLanguage approaches make no structural changes to the WordPress itself, and hence should be easier maintain. No extra magic in xLanguage is needed to keep the commenting, searching, popularity counter works.
Compare to Language Switcher v1.11 (Jan 2008)
This is actually the plugin that inspired me to build the xLanguage. The Language Switcher and the xLanguage is working in a very similar way — Both enable multilingual post by tagging the it. The Language Switcher uses square bracket instead of HTML tag, but have no assisting tools when composing the post. The language code is limited to the length of 2, and offer no overlapping possibility. Same as xLanguage, it allows user to enable multilingual functionality on single line content like tag, title and such.
Compare to jLanguage v1.4 (Jan 2008)
Almost the same as Language Switcher, both functionality and working principle. However, jLanguage v1.4 does not have widget for user to select their favorite language. In addition, It currently offer almost no customization, plus it does not work for single line content. The language selection could not affect the MO file selection.
It enables the language tagging by using square brakets instead of standard tag, similar to that of Language Switcher.
Compare to Multilingual post v0.2 (Jan 2008)
Please be aware that Multilingual post v0.2 does not belong to this category at all. It does not enable poster to published mixed language in a post. The user also cannot selectively view the post in a particular language.
It only does insert the lang=”..” tag at the HEAD such that browser can render the page better. xLanguage also does this.
Compare to Bunny’s Language Linker v0.2 (Jan 2008)
Bunny’s Language Linker’s way to enable multilanguage blog is minimal and simple, yet the integration is very loose. It works like Gengo, the pros and cons compare to xLanguage is very similar.
Compare to Basic Bilingual v0.31 (Jan 2008)
Basic Bilingual v0.31 allows you to insert a summaries in a different language. It is yet another very simple plugin.
March 8th, 2010 at 22:49
Hi,
I’ve just installed the plugin but I don’ t really understand this message at all when I set up the permlinks options:
“Options cannot be saved because:
The permalinks supported mode must include the primary appending position.
The Square Bracket Syntax must be consists of a-z, A-Z, 0-9, – (dash) and _ (underscore) only.”
I choosed that on Primary Appending Position:
” Prefix looks like http://example.com/blogurl/lang/en/archives/123. This has better compability with other plugins”
And that on Square Bracket Syntax:
“/”
Any HELP please???
March 4th, 2010 at 9:18
This works:
blablebliThis does not work:
blablebliblo blo bloWhy?
March 4th, 2010 at 6:14
After I edit an article with Windows Live Writer all the text in the article is shown, regardless of the language. I must open it in WYSIWYG editor in WordPress and save it from there. Only then it looks OK again.
February 24th, 2010 at 15:27
Hi,
We are using your plugin xLanguage. It works great!! but we have a doubt. Now we are using ‘ugly’ permalinks like ‘http://xxxxx/?p=123′, and now we’d like to use pretty permalinks like ‘http://xxxxxx/2010/02/17/sample-post/’. I have tried to do it, but the permalinks are not good, because use the full title (english|spanish) like this ‘http://xxxxxxx/2010/02/17/english title spanish title/lang/en’.
Can I use your plugin with pretty permalinks like that? Please, explain me how.
Thanks in advance
February 20th, 2010 at 13:09
[...] My site is implemented in wordpress. I use the very nice atahualpa theme from bytesforall and a special plugin for multilingual websites, xLanguage from Sam Wong. [...]
February 19th, 2010 at 22:48
I am sorry the code wasn’t showed. Second try !
Hi there!
I found a bug on list_lang.php.
I am using flags. Active flag is showed perfect but the “no active” flag is not showed, after debugging I found the problem.
File: list_lang.php
Original:
<a href=\"\”>
<?php
Corriged:
<a href=\"\”>
<?php
February 19th, 2010 at 22:44
Hi there!
I found a bug on list_lang.php.
I am using flags. Active flag is showed perfect but the “no active” flag is not showed, after debugging I found the problem.
File: list_lang.php
Original:
<a href="”>
<?php
Corrected:
<a href="”>
<?php
February 19th, 2010 at 20:53
We are using your plugin xLanguage. It works great!! but we have a doubt. Now we are using ‘ugly’ permalinks like ‘http://xxxxx/?p=123′, and now we’d like to use pretty permalinks like ‘http://xxxxxx/2010/02/17/sample-post/’. I have tried to do it, but the permalinks are not good, because use the full title (english|spanish) like this ‘http://xxxxxxx/2010/02/17/english title spanish title/lang/en’.
Can I use your plugin with pretty permalinks like that? Please, explain me how.
Thanks in advance
February 16th, 2010 at 8:27
Yes. Seems that have some issues with Chrome.
February 15th, 2010 at 15:22
At first thank you very much the nice plugin. This really works great. However, I want to put the language switcher in the header (not as a sidebar widget). How can I do that. I guess, I have to edit header.php. Thanks
February 15th, 2010 at 13:42
There’s literally hundreds of opportunities out there, including local groups, but I’m going to list some of the best online penpal sites and my experiences with them. Thanks alot for the plugin by the way. Appreciate it. Cheers
February 12th, 2010 at 19:03
[...] Ja no faig servir Polyglot per a les traduccions sinó xLanguage, molt més potent i fàcil d’utilitzar. A més, he doblat el tema per tal que la interfície [...]
February 10th, 2010 at 23:32
One of the best ways of learning a language is interacting with natives. There’s literally hundreds of opportunities out there, including local groups, but I’m going to list some of the best online penpal sites and my experiences with them.
February 10th, 2010 at 3:17
Hello Sam and all the folks who are helping throughout the comments. First of all I would like to thank you for this great plugin and for the support you are offering.
I have a question I couldn’t solve after going through the 770+ comments.
I’m trying to apply the translation to widgets. It works fine with titles. It also works fine with text… while it is a single line text. But, what if the content of the widget is something more complicated, ie, a bunch of HTML with more than one single line? Could I use the “normal” text option, ie, the span tags? It seems I can’t, but maybe I haven’t done it properly.
Any help out there? Any workaround?
Thank you very much.
February 10th, 2010 at 2:05
it works perfectly; just be sure to double check how the admin side works in chrome tho as i have spent many hours trying to figure out why the plugin wasn’t working and eventually i have tried to use in firefox and it was a browser issue, i’m talking about applying a language to the text from the admin panel, in chrome doesn’t let you do it while in firefox worked as a charm.
Thanks a lot for you effort, it’s brilliant.
February 9th, 2010 at 3:00
[...] fois trouver, il me fallait un plug-in pour avoir un site bilingue, parmi la multitude de choix, xLanguage a retenu mon attention, notamment car il permet de traduire les menus et les titres en plus des [...]
February 8th, 2010 at 1:29
I cannot upload the widget to my navbar … it simply will not accept it … any idea why?
February 7th, 2010 at 22:46
This plugin works by inserting W3C standardized tag in the post content, and a XML parser will be involved to extract them when served, extracting all elements with the matching lang=”..” tag. The permalinks and RSS feeds are also presented correctly. For single line data such as post title, a special but simple syntax is introduced.