(Never mind, I can see that I need even more non-wiki setup, so I need to look into my old GoogleTranslate, or use some external translation tool... :-/ )
Jump to navigation Jump to search
Reply to "Is there a way to make this work with WikiEditor"
Reply to "How to use it on a private wiki?"
Reply to "Problem with finding article, when try to translate"
Reply to "Installation on a Wiki Family Sharing same resources and without CentralAuth"
Reply to "ContentTranslation with Interlanguages from Interwiki links"
Reply to "delete drafts from dashboard"
Reply to ""Your" language"
About this board
This board is for discussing technical details of the Content Translation extension. If you are not a developer interested in installing the tool in your own system or contribute new code for it, this is probably not the discussion page you are looking for.
Check the discussion page for Content Translation for general discussion about the tool, reporting issues you found while translating, discuss its design or suggesting improvements.
Is there a way to make this work with WikiEditor
How to use it on a private wiki?
Now it will raise a "cx-error-page-not-found" exception if set wgGroupPermissions['*']['read'] = false; . So is there some idea ?
Problem with finding article, when try to translate
I would like to complain about translation page. When I try to translate, for example, from be-tarask (article Васіль Захарка) into Ukrainian, I just can`t find article and can`t translate.
But, when I do the same action from simple Belorussian to Ukrainian, there is no problem with finding article. What`s the problem?
I can see error when opening be-tarask page in translator .(⧼cx-error-page-not-found⧽)
It seems this is a bug.
Installation on a Wiki Family Sharing same resources and without CentralAuth
I am setting up a new wiki Family on my server using the "Multiple wikis sharing common resources" method. the url setup is like this:
https://wiki.mywebsite.com/en for English, https://wiki.mywebsite.com/de for German...etc
Since it is a new installation, I don't have CentralAuth, I was thinking of using a shared database as suggested by the CentralAuth Extension documentation here.
I read your discussion from a couple of years ago, but I am unable to determine the following:
1- Can the extension translate page names? so can I achieve:
https://wiki.mywebsite.com/en/the_Sun for English, https://wiki.mywebsite.com/de/Die_Sonne for German?
2- Can it work with the type of wikifamily I mentioned above?
3- Can it work withthe shared db, in lieu of the CentralAuth extension?
4- Does it translate Category names?
Thanks a lot.
- Yes, in Content Translation you can give the page any name you want.
- I'm not sure that I understand the kind of wiki family you have. Is it CentralAuth or not? I certainly recommend CentralAuth, because it will allow interlanguage links like in Wikipedia, and clean separation between each language version. It will work also without CentralAuth, and it will simply publish everything to the same wiki, and you'll either have to tell your users to take care of the naming, or to add a patch to Content Translation that will give such names automatically. (We only focus on Wikipedia's needs, but patches that add support for other kinds of architectures are very sincerely welcome.)
- Yes, it has its own shared DB. See the "Translation database" section. CentralAuth is highly recommended for convenient user account handling and separation between languages. It's a bit tricky to set up (to be honest, the last time I did it myself was in 2012), but it's much more convenient once it's done.
- Yes, but only if:
- You set up separate wikis.
- You set up interlanguage links.
- The corresponding category pages exist on both wikis, and are linked using an interlanguage link.
@Amire80 Thanks you very much for the detailed response.
As for the type of wiki family I have, it is the "Multiple wikis sharing common resources" (link to the exact spot in the documentation). I currently don't have CentralAuth, as the centralAuth documentation advise against installing it for new fresh wiki installation. Please check the link here under (Warning).
However, I will get it installed to reap the benefits you mentioned.
As the video demonstration of the Content translation Extension page on Youtube (link) shows the titles as: "https://en.site..etc", https://ca.site..etc, my question was whether there are settings to modify this to be: "https://site..cet/en" "https://site..cet/ca" ? Or is the extension just following the setup of the wiki family and produce content accordingly?
If I'm not mistaken, you'll have to define a custom value for ContentTranslationSiteTemplates. See the file extension.json in the ContentTranslation extension source code for this variable's components. @Nikerabbit may have more precise information.
(And yes, we really should document all these configuration variables.)
Even though at the moment we only have time for making ContentTranslation work with Wikipedia, we do hope that it is useful on other sites as well.
ContentTranslation with Interlanguages from Interwiki links
Hi, I maintain several mediawikis of several languages. Can I use this extension to make easier translate content between them? Or this is only an extension ready to be used just within the same installation? (don't using Interwiki links en.wiki.com/wiki/article using wiki.com/wiki/article/en instead?
Thanks a lot for the interest!
It should be possible, and if it isn't, it's a bug.
As our FAQ says, we are developing this extension with Wikipedia in mind, so the default configuration definitely has a bias towards Wikipedia itself and sites with a similar configuration. However, most of it is just a MediaWiki extension, so it should work with careful configuration.
If you get stuck, please ask here or report a bug in Phabricator.
I was searching a lot in Meta and in Mediawiki.org about how Wikimedia foundation does it in Wikipedia.org and there's not a clear information! It is a wiki familiy or what? Thanks if you know it.
Yes, ContentTranslation is definitely oriented at wiki families, with domains in the form of LANGUAGE_CODE.DOMAIN.TLD (this is configurable), and we pretty much assume that CentralAuth is used for usernames (by its nature ContentTranslation is cross-project, so the usernames should be cross-project as well, and if you aren't using CentralAuth, we don't know how will user accounts behave - we never tested it).
I suggest trying to install it and see what breaks ;)
Bugs and patches are seriously welcome - in practice we are working exclusively on Wikipedia integration.
CX doesn't need updates in the usual MediaWiki database tables, but it does use an extra database for the drafts. I'm wondering how to note this here. The needs-updatephp parameter is for update.php, and this doesn't currently works with update.php, and it isn't required.
Out of curiosity, why can't those tables be created in one of the existing central databases?
The CX database tables co-exist with existing shared central database(centralauth use the same).
delete drafts from dashboard
Is it currently possible to delete drafts from the dashboard?
It is in progress. See https://phabricator.wikimedia.org/T75979
Thanks, I had already subscribed to it.
got here from wmblabs beta wikipedia thing.
description of the content translation tool says:
"Shows a red link to your language in the language links list if the page is not yet translated to your language"
if i am using a wiki farm where i have a SUL account on 4 russian wikis and 4 english wikis, then i need to set 'my language' to 'english' on the russian ones in order for this tool to show a red link?
this is somewhat inconvenient, i speak 2 languages, i should be able to tell both to the entire wiki farm easily - not to tell 'hi russian wikipedia, my language is english'
or did i misinterpret what the meaning of that sentence is?
The red interlanguage link will be shown based on a prediction algorithm. So it is not entirely based on what language you set for your account in any wiki. This algorithm is somewhat similar to the algorithm we use in ULS to suggest languages to choose quickly. The algorithm will be tuned further, but the following will be used to predict - your language preference, your user interface language(changed using ULS), your previous UI language selections, the accept-language of your browser(the one you set in browser configurations), the geo-location from you browse the wiki and common languages in that location. What we implemented right now is a simple version of this algorithm. Also, we plan to provide more entry points than interlanguage link to tell user about the opportunity to translate. Thanks.
The algorithm sounds like an overcomplication. It may be a good idea to just ask me what languages I know, and offer that I translate to these.
I have added a picture of one more entry point there.
There are no older topics