Multilanguage is an important requirement for us. On government sites of Canada, Switzerland, Belgium and other countries, the multilingualisation of government sites are mandatory. Most of our clients speak their mother tongue plus English. In Europe, many people know at least another language. The multilingual features of Postnuke and all its forks are not implemented consistently. Here are my pet peeves and suggestions for improvements for PN .8
1) Header, footer, site name, slogan and logo. I fail to see why the header, footer, site name, slogan and logo are not multilingual. Like news, there should be a language selector. Currently, there is a hack in the solution forum, but it should be in the core.
2) Downloads, Web Links, Topics and other standard PN modules. There should be a language selector when adding a download, web link, topic, etc... . I should be able to write a description and category in English or French or Spanish for the download and select a language saying that it is meant for English, French or Spanish or All. Then when the current language is switched to French, the French categories and descriptions of downloads are displayed. The same for Web link, Topic, etc ...
3) Anything that requires the user to input, to write should have a language selector beside it specifying what language it is meant to be.
4) Third-party modules. To all developers, please add multilingual features to your modules, add-ons, components. And to the PN's core team, please make it easy for developers to develop multilingual modules.
Thanks and all the best to future MULTILINGUAL releases of Postnuke!
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
Forum Activity
- alfonsomarin created topic »Fillters in Clip« 03:41 AM
- damon responded to »Can the Updated Version Check be Turned Off (Z 1.3)« 03:19 AM
- frw responded to »Bug in the SMTP mail transfer protocol - Port 25 - Zikula 1.2.9« 22. May
- mdee responded to »Short URL questions« 22. May
- mesteele101 responded to »Problem in Database Connection« 21. May
- Herr.Vorragend responded to »Clip Documentation and Doubt« 19. May
- mazdev responded to »zikula 1.3.3. and IE9« 19. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
Improvements on multilanguage for PN .8
-
**unknown user**
- Rank: Freshman
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 68
Posted: Feb 02, 2004 - 04:01 AM
-
**unknown user**
- Rank: Softmore
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 275
Posted: Feb 02, 2004 - 03:18 PM
muy bien dicho!
athooya
3) Anything that requires the user to input, to write should have a language selector beside it specifying what language it is meant to be.
Best to have an option whereby the user's choice generates these, around the text in the article (in the case of Spanish, for example):
This is being implemented manually at http://www.issho.org/backend.php .
rather tedious work. -
**unknown user**
- Rank: Freshman
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 68
Posted: Feb 03, 2004 - 12:30 AM
Quote
3) Anything that requires the user to input, to write should have a language selector beside it specifying what language it is meant to be.
What I mean by this is that on any form that requires the user to input, the form should have a language choice. The "submit news" and "add stories" forms have the language choice, why don't the Downloads, Web Links forms not have a language choice as well ?? That way, when language is switched to Spanish, the categories/descriptions of Downloads and Web Links are switched to Spanish too.
From a developper's implementation point of view, I guess this means adding a language filed (pn_language) to the tables of Downloads, Web Links and other tables.
I hope PN .8 would remedy these inconsistencies in the multilanguage. -
**unknown user**
- Rank: Softmore
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 275
Posted: Feb 03, 2004 - 03:02 PM
athooya
From a developper's implementation point of view, I guess this means adding a language filed (pn_language) to the tables of Downloads, Web Links and other tables.
Yes, that certainly should be implemented, as well! -
- Rank: Expert
- Registered: Mar 11, 2003
- Last visit: Oct 21, 2009
- Posts: 1104
Posted: Feb 06, 2004 - 06:36 AM
Something I have done on occasion, which is really a dirty solution, is duplicate a module and its tables (renamed of course) and dedicated it to one of the three languages I serve. Again, it's not pretty but it works and, when put into the menu for the language, works pretty well.
Of course the theory here is that, particularly for forums, users don't want to try to follow a thread through several languages and back.
As for the forms, lets say I have an address book and under profession I put baker. Regardless of which language I'm using the profession entered would normally read "baker". I've fixed this in two ways. One way is to create tables with the _BAKER version and add to the language files that translate that. The other is to write _Baker directly into my form again to be translated the regular way. Which method I use really depends on how fluid I want to be and how badly I need to save myself from yet another query. Take care with this because you'll drive yourself nuts trying to keep up with the upgrades.
Slugger
- Moderated by:
- Support
