SMF Community Helpers > SMF Documentation Help
Wiki translation
emanuele:
No, the translation feature as it is applied to certain pages (those that are part of the help in SMF's help menu) here at wiki.sm.org it's not a WikiMedia built in feature, it comes from an extension.
There are a couple of reasons why I would avoid apply the translate extension to the entire wiki:
1) the use of the extension reduces the freedom to manage the pages (when you "mark a page for translation" then you cannot do certain basic tasks like move and delete the page, and also redirects become a pain, I don't remember the details because it's a while I don't try to do such operations on translatable pages...),
2) using the translate extension has few drawbacks on the wiki-syntax for links, templates, categories, etc. (we had to replace the links with a template for example to be able to directly link the appropriate language instead of having all the links in all the languages go to the English page, I'm pretty sure I discussed this point with Agridoc here in this board)
3) most likely not all the pages need a translation.
BTW the translate extension is a good tool when keep the pages synchronized is important, so IMHO it's fine to use it when it's necessary (i.e. on a limited number of pages, those that actually need to have the same look&feel), but if we want to translate more it would be better to rely on users' good will and organization and define few internal rules (or guidelines if you want) and stick to them (I think there is a topic on that too here around).
* emanuele still feels the yellow badge on him. :P
AngelinaBelle:
That is a good answer, Emmanuele.
At this time, the translate extension simply has certain problems. And a couple of bugs.
I think that, if the translate extension gets improved, I would be willing to add it to more articles.
Right now, using the translate extension requires someone to fiddle with the carriage returns, and replace links and even images with wiki-templates. It is a much bigger pain than it was meant to be. It is currently easier to simply create the sub-page. I am not sure how this would affect the ability to use the translate extension on the same article in the future, however. We don't have a "test wiki" to test such things on.
GravuTrad:
So why this wiki isn't still in the beta stage??
An official release need a stable stage, not a buggy one.
Maybe doc creation was privileged? (it could be understandable so, but public beta was sufficient for this...)
It's sure that if the translate extension development is slow, we are tributary of this but can't wait all to advance...
Over mediawiki sites have these problem with this extension?
emanuele:
Sorry GravuTrad, but I can't follow you here.
The wiki was in beta in order to test things. Now the testing is finished the "beta" status has been removed.
The translate extension is a tool that can be used for translations, but it's not mandatory to use it, wikimedia foundation doesn't use it on wikipedia.
We decided to use the translate extension on the pages that must be kept in sync (i.e. those used in the help page of SMF...I hate repeat myself, sorry) and not on the other pages.
The other pages can be translated without the translate extension. It's not that this means the other pages are "category b", it simply means we are using two different tools for the job.
AngelinaBelle:
The translate extension has had a lot of work lately.
So I'd like to try it -- after the wiki is upgraded to 1.18 at least, because 1.18 will be required for new versions of the translate extension.
I do not know when it would be possible to have the wiki up to version 1.18, but I have asked SleePy
We'll see.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version