Multilingual support on slashcode templates
Hi everybody!
We've started improving the multilingual support on slashcode because we need it for the European Social Consulta first phase web page (http://www.consultaeuropea.org).
As far as we know, currently there's not multilingual support, the suggestions are to translate all the template files... But in our case we need to show the interface in multiple languages, as we're developing a system to translate the postings. So first of all, we wonder if there is somebody working on it, because we saw the lists about i18n really empty. Is anybody doing some stuff about multilingual slashcode? On the second hand we expose our idea, to know what do you think about it, and if is somebody interested in working in parallel. We planned to hack the "Slash::DB::..." improving funcs like: "getTemplateByName" to get the users lang like: "$lang = getCurrentUser('lang')" and include it when building the answer: answer = $self->sqlSelectHashref('*', "templates", "tpid=$id, lang=$lang"); because the slash DB table templates already has a 'lang' field. BTW, who is 'in charge' of this field in the DB? who's working with it? The matter is, that the tpid is a primary key, so it cannot be more than one template with the same id, even if they're in different languages.Then our suggestion is to add a new parameter in the table_cache_id of the db object, like: "my $id = $self->{$table_cache_id}{$name, $page, $section, $lang };" What do you thing? Did anybody try it?
thanks! Krow (aka brian): I put the field in for this reason but we do not currently make use of it ourselves.
We've started improving the multilingual support on slashcode because we need it for the European Social Consulta first phase web page (http://www.consultaeuropea.org).
As far as we know, currently there's not multilingual support, the suggestions are to translate all the template files... But in our case we need to show the interface in multiple languages, as we're developing a system to translate the postings. So first of all, we wonder if there is somebody working on it, because we saw the lists about i18n really empty. Is anybody doing some stuff about multilingual slashcode? On the second hand we expose our idea, to know what do you think about it, and if is somebody interested in working in parallel. We planned to hack the "Slash::DB::..." improving funcs like: "getTemplateByName" to get the users lang like: "$lang = getCurrentUser('lang')" and include it when building the answer: answer = $self->sqlSelectHashref('*', "templates", "tpid=$id, lang=$lang"); because the slash DB table templates already has a 'lang' field. BTW, who is 'in charge' of this field in the DB? who's working with it? The matter is, that the tpid is a primary key, so it cannot be more than one template with the same id, even if they're in different languages.Then our suggestion is to add a new parameter in the table_cache_id of the db object, like: "my $id = $self->{$table_cache_id}{$name, $page, $section, $lang };" What do you thing? Did anybody try it?
thanks! Krow (aka brian): I put the field in for this reason but we do not currently make use of it ourselves.
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Why a multilingual Slash? (Score:2)
Let me clarify: Slash is a CMS (Content Management System) that couples an article-management part with the great public comments part. All these texts are written in some specific language, so even if you plan to support let's say English, Italian and Spanish, you will have stories in English with attached
Check out the Slash in Italian Project [kenobi.it]
Re:Why a multilingual Slash? (Score:2)
1. If slash has all of it's stock templates translated to different languages, I'd guess that the use of Slash would increase more across other contries then the US.
2. It'd save people a lot of work if the code were setup properly to use different language settings appropriately.
And as far as comments being in a specific language - you really cannot control what people post. You can mod it up/down, delete it, but that's it, so if one user types in French and the next user posts a comment to the discussionthread that's in English - not much you can do.
Infact, I don't ever recall seeing anything in the schema to deal with lang and comments. There's no need imho.
lottadot [lottadot.com]
Need for a "simultaneous" multilingual slash... (Score:1)
I see what you mention about having same slash configuration in "two" sites with different languges, what I think is really good for projects like worldsbk.com
The matter is that in our case we really need a "simultaneos" multilingual slash, because we planned to translate the user posts.
How? well, in the European Social Consulta project there are going to be Promoter Groups able to translate into english people posts. They will be helped by automatic translation machines from different languages, and we'll give the user herself/himself the opportunity to do the translation. (you can see page 16 of the specifications http://www.consultaeuropea.org/tech/webspecs.pdf)
This is an special project, to discuss issues around Europe, so we need this feature. We hope, that lately it will be useful for other similar projects, specially in Europe where we have such amount of different languages.
I hope this can clarify why we need a "simultaneous" multilingual slash, and maybe there is more people interested in this feature.
Thanks a lot for these first comments!
Re:Need for a "simultaneous" multilingual slash... (Score:1)
I would wonder about the server impact, like translating large amounts of comments at the whim of a web surfer. I'd also be concerned about thing being lost in the translation; sometimes the "fish" makes for some funny translating ;)
--
Kill-HUP.com [kill-hup.com], proudly running Slash since 1/28/2002.
Re:Why a multilingual Slash? (Score:0)