Next updates of the xLanguage
Saturday, February 2nd, 2008
唔好意思，呢篇文無粵語版。
Wow. The xLanguage plugin have got quite amount of feedbacks. Many thanks to everyone.
Here is the tentative list of things that will go into the next updates
Feature-wise
- Language Fallback
So a post with no matching available language can show a fallback / default language, instead of just the missing text. - Different default language settings for Browser and Robot
- A different parser — Square Bracket
The XHTML parser is too strict and breaks a lot of thing. The TinyMCE code work best in Firefox 2, and might only work best in Firefox 2. By using square bracket style, both the parser and the TinyMCE toolbar will play much nicer and have higher degree of tolerance. But the lang=”…” tag in this mode will gone, which might affect the presentation in special combination of fallback and RTL/LTR language. - WP-Cache and WP-SuperCache compatibility
- Parser error log
So that you can find out all of the page that failed in the XHTML Parsing. - Usage feedback (of course you need to opt-in)
Let me get the feedback about how the module is being used. - Toolbar hotkey
Isn’t it too troublesome to click the toolbar button - Template functions for doing translation
A quick (but dirty) way to do translation without touching the official gettext. - *_description filter should have single line filtering mode enabled
Enable simple splitter character to be used in category description and so on.
Security-wise
- Admin page Nonce
- Bar the test script from being executed from Web
Documentation-wise
- Configuration with Fallback enabled
- Configuration with WP-Cache and WP-SuperCache
- How to enable xLanguage filtering on Widgets, Template and Plugins
- Instruction for RTL
- Promote the filter ‘language’.
Every localization plugin like xLanguage should hook into this. Every plugin that allows customized text should have it filtered by this.
Entry was posted on 2 February 2008 at 1:07.
Category xLanguage (WordPress), 通知
Comment 
| Commends and pings OK
中文
粵語
February 3rd, 2008 at 20:18
Hi,
Many thanks for your great plug-in, that’s exactly what I needed.
In certain cases (in particular when I put a link I believe but I’m not sure), some text appears indefinitely on the web page, although it’s everything fine from the admin dashboard.
I spent all last night doing tests to clean up, to write again… and I don’t see where does the problem come from.
This morning I finally deactivated the plugin and the problem disappeared.
But I really need what your plug-in does…
In the final webpage source, I see mis-written code: </xLanguageP
Can you help me on this?
Many thanks
February 4th, 2008 at 0:01
Croisillon: Basically I have another user reporting the same problem. Would you mind emailing me (sam /at/ hellosam.net) the source html code that you used? I will try my best to find out the root of the problem.
February 5th, 2008 at 2:37
Hi Sam,
I’m already translating my entire website because of this plug-in
I’m just missing the theme translation function. In order to support RTL/LTR properly the best thing is to support multiple themes using a different sub-directory for each language (under your favorite theme directory). That way you can show your website in an entirely different way if another language was selected. I can’t see any other way to make a website showing from !body dir=’rtl! to !body dir=’ltr’! and the same goes for all other divs and elements.
February 5th, 2008 at 14:29
It’s good to know you are using it— Even me didn’t have the time to translate the theme yet, haha.
I think the best way to do is to selectively include a suitable CSS depends on the language.
The css then could say “body { direction: rtl; }”, with other necessary layout changes.
I will include the ability to changes theme per language, and a template function to get the currently used language. But I still think maintaining a single theme + css will be a better solution.
February 5th, 2008 at 16:07
CSS could work nicely with proper adjustments so yes it’s a great idea. I totally agree with you about maintaining two themes.
Two themes could also help in case language related images are used as part of the theme, although this can also be resolved with CSS classes. I’ll be waiting for next version
February 18th, 2008 at 5:13
[...] Monday, February 18th, 2008 As I have mentioned in the eariler post, I was working to fix some critical bugs and at the same time putting some more features into the [...]