Page MenuHomePhabricator

[Migrated] AutoWikiBrowser internationalisation and localisation
Open, MediumPublic

Assigned To
Authored By
May 28 2015, 1:14 PM
Referenced Files
"Like" token, awarded by Elisardojm."Like" token, awarded by Davisuke."Like" token, awarded by Sunpriat2."Like" token, awarded by Liuxinyu970226."Like" token, awarded by Kizule.


50% of the WMF traffic is not English. If this software is useful for other languages, it should be possible to use the software in this other language.

Related Objects

Event Timeline

Reguyla raised the priority of this task from to Needs Triage.
Reguyla updated the task description. (Show Details)
Reguyla added a project: AutoWikiBrowser.
Reguyla moved this task to Feature request (unsorted) on the AutoWikiBrowser board.
Reguyla added subscribers: Reguyla, Aklapper.

@Reedy 11:06, 1 December 2008 (UTC) wrote:
You can use it on any language (as of the svn version), just the interface isn't localised.

@Reedy 11:13, 1 December 2008 (UTC) wrote:
As an aside. We have thought about it, and it would be a good idea. It just would require a lot of reworking of the code, and the interface changing to cater for the larger text aswell... Getting translators would be easy enough, i suspect.

@Dispenser 16:48, 1 December 2008 (UTC) wrote:
I haven't found an easy to non-standard Windows font PPI since the window resizing modes doesn't seem to have an "em" mode. The best I've been able to come up with is using dymaic layout boxes, but that tends to slows redrawing.

@Helder 18:21, 15 August 2013 (UTC) wrote:

@Magioladitis 18:52, 15 August 2013 (UTC) wrote:
We now provide edit summaries in many languages and the set of rules are better localised for the various projects. I call for help in order to expand the localised edit settings to more languages.

Josve05a subscribed.

We could integrate AWB with (as programs as Huggle) has done. This would cause the interface to be in multiple languages.

We could integrate AWB with (as programs as Huggle) has done. This would cause the interface to be in multiple languages.

There's quite a few big steps missing here :)

There's quite a few big steps missing here :)

Of course, just thinking of a way we could reach I18n. How to do it, is another problem.

Amire80 renamed this task from [Migrated] Internationalisation and localisation to [Migrated] AutoWikiBrowser internationalisation and localisation.Aug 30 2015, 10:55 AM
Amire80 triaged this task as Medium priority.
Amire80 set Security to None.


On Wikipedia in French, we recently raised the problem of the lack of inter-agencyization for the AutoWikiBrowser software. Is it possible to add an i18n system, for the AutoWikiBrowser software, which could be powered by for example ?

Best regards,

Florian COLLIN

As per previous comments, yes it is possible. But it's not a small amount of work, and it needs people to have the time to actually work on it

Hello, and thanks for your answer,

If I may : what would be the process for an i18n installation on AutoWikiBrowser. So I will try to say it with my English : the code to insert, the pages to create if necessary...


Florian COLLIN

There's different ways to do it in .NET, but I haven't actually ever had to do it. AWB isn't setup to allow this easily at all currently.

The code/UI needs migrating to loading strings from presumably a resource file or similar, and then those files being made available in some way to allow translation...

Potentially. I imagine there's a few different ways to do this

But there's still a lot of work to move all the strings into one place, and plumb them back in...