Because this is what comes up when you click the link to the wiki...
Fyi, it says "parked at Loopia"; some guy owns it. So... you guys know what's up? I'm all for translating the Installation and Beginner's Guide by the way.
]]>I'm just announcing that in the next few days Template:i18n will be deprecated and replaced by interlanguage links (e.g. [[en:Title]]) also for the languages hosted locally. This operation will be completely performed by a bot. For more information, see https://wiki.archlinux.org/index.php/He … plate:i18n and https://wiki.archlinux.org/index.php/Ar … nalization.
]]>See http://meta.wikimedia.org/wiki/Help:Export and http://meta.wikimedia.org/wiki/Help:Import for additional information.
As long as your wiki uses the GFDL license (which it does) there should be no license concerns.
One problem you might run into concerns duplicate user names. That is, if UserA contributed to an article on this wiki, you import the article and its history on your wiki, and there exists or someone creates an account with name "UserA" that is not the same individual represented by that user name on this wiki.
*Edit*:
Regarding update of interwiki links: After you have imported a page to your wiki, please edit the page here to redirect to your wiki. For example, after importing Pacman (Français), change its content here to #REDIRECT [[fr:Pacman]].
I have added interwiki language links to the Main Page and pacman pages.
]]>Is there some guide on how to update interwiki links or it's only manual ?
(Maybe a bot account per site?)
If not, can you please add links for the protected pages:
[fr:Accueil]] for "Main Page" and [[fr:Pacman]] for Pacman's page
One last question, is there some specific things to do to import translated pages to our wiki regarding license and contributors ?
We plan to import all pages in Category:Français with their history (so contributors names will remain), is this ok ?
thanks.
]]>Benefits are:
Improved searches (default searches in English, users can select to search in specific languages)
Improved Recent changes page (can be limited to specific namespaces/language)
No hosting or sub domains needed for local wikis
Interwiki links set up pointing to namespaces behave like off-wiki interwiki links
No need for multiple user accounts if you want to edit both English and localized articles
Links from localized pages to English pages still work after the move
You don’t need to know the language to move articles, as no meaning is added to the pages, just organization
This would increase the number of namespaces, but that is a lot better than the current solution with all languages being mixed.
Do wiki Admins or Maintainers have access to MediaWiki maintenance scripts? There’s MoveBatch that takes a file of “existing name|new name” lines. If that can be used to move pages to a new namespace I can set up such a file for the Swedish articles and perform the Interwiki linking after they have been moved.
]]>I am in the process of copying all the translations over. I'd appreciate any help getting the interlanguage links working.
]]>I guess the long-term solution would be separate local wikis per language hosted by the same people hosting the main wiki. Three drawbacks with local wikis are that you would need to register separate accounts to edit different wikis, it’s harder to handle spam if the localized wikis don’t have users patrolling them regularly and you don’t move user accounts. I don’t think those drawbacks should stop us from cleaning up the main namespace, but maybe there are other solutions apart from hosting multiple wikis I haven’t considered.
Is it possible to get a Swedish wiki running at a sub-domain of archlinux.org with interwiki links set up to and from the English wiki? Preferably updating the MediaWiki software would not be handled on a per-wiki basis because rarely used languages would soon use older versions. All wikis should be upgraded at the same time and use the same configuration.
In the Swedish pages links pointing to the English articles would break after a move. The solution I prefer is using redirect pages. That way, if you create a Swedish pacman pag,e you don’t have to modify any links in other pages.
The work flow would be:
Set up localized wiki.
Update interwiki settings.
Leave a message on the talk page of a couple of contributors of the localized pages.
Move page (using transwiki importing).
If needed clean up links by adding redirects back to the English main wiki.
Update interwiki links to and from the English wiki.
Repeat step 3-6 for all pages.
(Optional) Translate page titles to localized versions.
Repeat step 1-8 for each language.
Does that sound about right? I can set up a wiki page for coordination if this is the way to go.
]]>That way we could also find out if there are local communities without their own wiki and why. I am sure whatever the issues are here they can be solved. That's way cleaner and future proof than trying to have more than one language in one wiki.
]]>You then setup the interwiki links to point to each new namespace and move the pages of a language there. Interwiki links are added to the English pages pointing to translated pages, and they get an interwiki link pointing back to the English article in the Main namespace. The i18n template can be dropped as pages are moved. If a language gets an external wiki in the future, pages can be moved there and the the interwiki configuration updated without changing the interwiki links of the English pages.
It's great that information is available in multiple languages, but pages keep getting added to the wiki according to the i18n template instructions. When you search for "laptop", you don't want the first result to be Czech, the third to be the article in English and the sixth and seventh results to be the same page in Italian and Russian.
I can help move pages and add interwiki links if this sounds like a good idea.
]]>stefanwilkens wrote:Can the search function be modified to only search articles in the default language, set by the user?
I would like to know if this is possible too.
I don't think it's possible. archdocumentalist from AUR tried to solve this but there's no simple way atm.
]]>Can the search function be modified to only search articles in the default language, set by the user?
I would like to know if this is possible too.
]]>I realize you've chosen a path, just coining a thought in case it hadn't been coined before.
]]>