Jump to navigation Jump to search

Note Problems? Questions? Suggestions? Write your message below. – See also the FAQ or try to catch us in IRC.

Your request has been forgotten? It's suggested to use {{Support}} in thread summaries, see also documentation.


Thread titleRepliesLast modified
Is it possible to merge two users?623:11, 20 December 2018
Adding DSpace1013:49, 19 December 2018
Checks on Wikimedia:Wikipedia-library-ae475f-=7B=7BPLURAL:GETTEXT=7CContact=7CConta/en620:13, 17 December 2018
Delete account or change username to sth anonymous022:15, 16 December 2018
Translate bug: Misidentifies which version of /en message is the latest1223:23, 11 December 2018
About capital letters "KP"009:52, 7 December 2018
cannot PREVIEW my text when writing a message for Support020:02, 3 December 2018
irc help requested "Cannot send to nick/channel"420:28, 30 November 2018
translating webhook ?315:59, 28 November 2018
Spelling mistake in MAZI:portal-admin.general.reboot-modal-message/en112:44, 28 November 2018
Requesting activation of Seereer and the Cangin languages, and translator rights 004:18, 25 November 2018
Block "BadDog"420:03, 21 November 2018
Πληρωμή Μεταφράσεων στους Συνεισφέροντες στο www.translatewiki.net013:49, 19 November 2018
Cantonese disappearing everywhere in translatewiki208:23, 15 November 2018
Fallback language of kjp (Eastern pwo)005:02, 13 November 2018
Permissions error in saving translation216:20, 8 November 2018
LibreRouter: new project with software and HowTo booklets1515:23, 6 November 2018
Request for rights (Zoranzoki21)319:08, 5 November 2018
Problem with publishing translations115:20, 3 November 2018
#Babel translations for muiwiki in Incubator115:36, 1 November 2018
First page
First page
Last page
Last page

Is it possible to merge two users?

Hi, For some reason I've got two user accounts on, probably due to a misunderstanding concerning username and a display-name, or even the fact that my display-name contains a special UTF-8 letter.

I'm currently using Sveinn í Felli but my old login was Sveinki. It would be nice (and useful for avoiding misunderstandings) to have this latter account point to the former, or to merge them so that Sveinn í Felli becomes prevailing.

Is this possible?

Sveinn í Felli (talk)09:29, 2 February 2018

Yes, this is on TWN, where we are not in the WMF instance, so we can try merging your two accounts.

Liuxinyu970226 (talk)09:43, 2 February 2018

Can you please do it?

Sveinn í Felli (talk)15:12, 2 February 2018

Should I send a specific request to someone? Where/Who?

Sveinn í Felli (talk)10:53, 15 August 2018

We don't have any user merge extension here and there's no plan to install it, so I'd just decline this request. User:Sveinki has less than 500 edits; User:Sveinn í Felli is older, has an email address and was used recently. If you just stop using "Sveinki", you'll be fine. I can block and/or rename the account you don't want to use and you can place a redirect from one username from the other. We can also recover the password of either account if you lost it and the email address doesn't work.

Nemo (talk)11:02, 15 August 2018

"you can place a redirect from one username from the other" - yes, that was in my initial request. How can I redirect User:Sveinki to User:Sveinn í Felli ?

Sveinn í Felli (talk)11:00, 4 December 2018

I've redirected them for you.

McDutchie (talk)23:08, 20 December 2018

Adding DSpace

DSpace is a mature open source project originally created by HP and MIT back in 2002, now supported by a non-profit Duraspace. It is a web based platform for institutional repositories, used by academic, non profit and corporate institutions to provide (open) access to hosted content.

Some examples:

We became interested through the website and when chatting with your contributors, who advised us to answer the following six questions as part of the request to be added as a project. We would like to enter a dialogue to see if we could get adopted and what that would entail exactly.

1) is your code open source?

Yes, the license files can be found on:

2) is your development active currently and to the foreseeable future?

Yes, DSpace is being actively developed under a time based release schedule. The draft of the release notes for our next major release end of 2013 can be found at:

3) what file formats do you use?

DSpace has two user interfaces, one based on JSP and one based on Apache Cocoon. The JSP User Interface uses Java properties:

The Apache Cocoon based interface uses an XML format, the standard Cocoon Catalog/Dictionary format described midway down the page here:

Actual files can be found here:

More information describing the current state of the DSpace internationalization efforts can be found on:

4) do you have resources to address reports from (like, requests for adding message documentation, fixing i18n issues in messages)?

Yes, the DSpace committers and other community members actively address such reports in the DSpace JIRA environment:

5) can you appoint a contact person

6) Are you okay for using only as the way to contribute translations

We would have to investigate the details of what this entails exactly, but in principal we will agree to this as long as: - it should be easy for people to provide translations - it should be easy for people running a DSpace installation to do local changes or additional translations within their own instance of DSpace if they would want to.

Bluyten (talk)23:03, 19 June 2013

Thanks for your interest. I've checked out the product and the license. I think there is definitely a basis to explore further. Thanks for considering

I've looked at the two file formats for i18n that you linked to. I wasn't able to identify the file containing the source texts, for example in Where are those files located?

As for the XML format in; we do not support that file format yet. I'm not really a developer, but I took a stab at adding support for it in gerrit:70602 based on the Android XML format support that we already have. Would it be possible that one of you completes the patch set?

Siebrand09:25, 26 June 2013

The original source for can be found here:

For the Cocoon XML format: I will try to find someone to look at your code and finish this.

Bluyten (talk)10:04, 27 June 2013

That's cool! We have some documentation for that at

Nike (talk)08:09, 1 July 2013

Just a quick note that we haven't forgotten about this and will follow up in due course.

Bluyten (talk)12:41, 25 July 2013

Thanks Bluyten, please let us know here of any roadblock.

Nemo (talk)13:51, 29 July 2013

What's with the checks that are preventing the message Wikimedia:Wikipedia-library-ae475f-=7B=7BPLURAL:GETTEXT=7CContact=7CConta/en from being translated? I get the error message "The following parameter is unknown: {{PLURAL:GETTEXT|Contacto|Contactos}". Isn't the message supposed to be translated?

Hamilton Abreu (talk)16:40, 23 October 2018

Hi, I no have this problem. Can you check again?

Zoranzoki21 (talk)20:19, 27 October 2018

It continues.

To check it yourself, click Wikimedia:Wikipedia-library-ae475f-=7B=7BPLURAL:GETTEXT=7CContact=7CConta/pt and click "Edit". It will show:


This is the translated message, with "Contact/s" translated to Portuguese. The message is fuzzied because of the error reported. Now, remove the "!!FUZZY!!" and save it. Edit it again and the "!!FUZZY!!" is still there, meaning that the problem continues.

Now look at all existing translations. All those that have been translated are coloured pink, meaning they have a problem. For those that are not coloured pink, most were initially translated to the target language, got the same error and then people put them in English to get rid of the error. The only exception is /fi, which was inserted by the bot already translated.

So, the problem most obviously exists! When you state that you do not have this problem, EXACTLY WHAT LANGUAGE DID YOU TRANSLATE THE MESSAGE TO SUCCESSFULLY without the problem? There is no successful translation of this message made by you.

Hamilton Abreu (talk)00:59, 28 October 2018

Shouldn't the check that is preventing translation of the words "Contact" and "Contacts" be removed?

Hamilton Abreu (talk)11:50, 22 November 2018


Hamilton Abreu (talk)23:24, 11 December 2018
Nike (talk)13:52, 17 December 2018

Confirmed. Many thanks.

Hamilton Abreu (talk)20:13, 17 December 2018

Delete account or change username to sth anonymous

Hi. I dont have any contribs. Could you please Delete account or change username to sth anonymous? Thanks

Yasinaydin (talk)22:15, 16 December 2018

Translate bug: Misidentifies which version of /en message is the latest

The translation interface is misidentifying which version of an /en message is the latest.

The original message MediaWiki:Interfaceadmin-info/en was changed, as follows:

Translate bug 1.png

The change was presented by the translation interface, and the /pt translation was updated accordingly, as follows:

Translate bug 2.png

Now, after this update, the translation interface seems to be misidentifying which version of the /en message is the latest, compares the new /pt translation to the old /en message, identifies three errors in the new /pt translation and requests translation back to the original version of the /en message:

Translate bug 3.png

I have purged the translation statistics page, and the problem continues.

Do you want to verify first if this is due to something local, or should it be reported in Phabricator?

Hamilton Abreu (talk)09:01, 2 September 2018

Here's something even funnier about this.

This single message is listed as belonging to two groups: "MediaWiki core" and the extension "Wikimedia Overrides":

Translate bug 4.png

It's the same message being listed in both groups.

That in itself is probably incorrect, right? No message can belong to core and to an extension, I believe.

Now, the situation reported above was for the first time the message is listed, under the first group, "MediaWiki core". If we go to the second time it is listed, under the group "Wikimedia Overrides", this is shown:

Translate bug 5.png

So, here, the /en content shown that is to be translated is the correct one: the new version of the /en message. This is the correct text.

But, the three errors reported are the same as previously: those that result from a comparison with the old /en message instead of the new /en message that is being presented.

Hamilton Abreu (talk)12:17, 2 September 2018

The other one is now prefixed with 'wmf-' and this should be resolved.

Nike (talk)07:21, 3 September 2018

Can you please re-check? The situation as I see it is still exactly as reported.

There are indeed three messages starting with 'wmf-' in three languages but none of them is English.

Hamilton Abreu (talk)13:09, 4 September 2018

Sorry I was too hasty. It should really be fixed now.

Nike (talk)07:21, 7 September 2018

Sorry to report that the situation we have now is:

  1. For the original messages with name MediaWiki:Interfaceadmin-info/XX, the old, outdated, revision of MediaWiki:Interfaceadmin-info/en is being presented for translation instead of the latest revision. This remains as reported initially, and that is wrong.
  2. Five new messages have been imported with the name MediaWiki:Wmf-interfaceadmin-info/XX. These should probably be deleted.
  3. Several new messages have been imported with the name MediaWiki:Wikimedia-interfaceadmin-info/XX. As far as I can see, these have been appropriately fuzzied and should all be correct.
Hamilton Abreu (talk)18:49, 7 September 2018

About capital letters "KP"

Hello. I don't know why bot create two category named Category:User ko-kp and Category:User ko-KP.

In this situation, how can I fix this babel's problem?


Garam (talk)09:51, 7 December 2018

cannot PREVIEW my text when writing a message for Support

On I have checked last Experiemntal [X] Mettre en évidence les sélecteurs CSS i18n.

When I write this message for support and click on the Preview button, the popup says the equivalent of 'you'll leave this page and loose your modifications' instead of showing the new formatting for possible correction (<= nok)

When I use the visual editor and ask the preview in a similare way for standard messages translations, the new formatting is well presented and the correction is possible (<= ok, normal behaviour).


ChristianW (talk)11:55, 28 November 2018

irc help requested "Cannot send to nick/channel"

Requesting help from

Status #mediawiki-i18nX
#mediawiki-i18n: channel | Software internationalization for open source projects | No public   logging
[12:29] == Wladek92 [5544512a@gateway/web/freenode/ip.XX.XX.XX.XX] has joined #mediawiki-i18n
[12:29] <Wladek92> hello all
[12:29] == Cannot send to nick/channel: #mediawiki-i18n
[12:29] <Wladek92> anyone ?
[12:29] == Cannot send to nick/channel: #mediawiki-i18n
Chat is dead ? or is there a channel problem ? .... nobody answers on IRC.
ChristianW (talk)11:39, 28 November 2018

As the error message "Cannot send to nick/channel: #mediawiki-i18n" hints, your message was not sent to the channel or channel users, I don't see it. Probably some kind of antispam measure from freenode. Try an IRC client like HexChat.

Nemo (talk)11:46, 28 November 2018
Edited by author.
Last edit: 20:20, 30 November 2018

strange because the connexion to the channel is accepted; so how can we be made "identified users" instead ?

= End of /MOTD command.
[12:29] == Usermode change: +i
[12:29] == gateway/web/freenode/ip.XX.XX.XX.XX is now your hidden host (set by syn.)
[12:29] -freenode-connect- Due to the persistent ongoing spam, all new connections are being set +R ('''block messages from unidentified users''') and will be scanned for vulnerabilities. This will not harm your computer, and vulnerable hosts will be notified.
[12:29] freenode-connect [frigg@freenode/utility-bot/frigg] requested CTCP VERSION from Wladek92:
[12:33] == Wladek92 is connecting from *@gateway/web/freenode/session XX.XX.XX.XX

--> If a channel is set to mode +r, you won't be able to join it unless you are registered <--
ChristianW (talk)12:11, 28 November 2018

Unfortunately due to large amounts of spam, keeping it all open was not possible.

Nike (talk)11:34, 30 November 2018

... so no possible usage of IRC ( as recommended in "See also the FAQ or try to catch us in IRC." for the time being.

ChristianW (talk)20:28, 30 November 2018

translating webhook ?

What are synonyms for that word ? what is behind ? A lot of messages to translate are concerned. Thanks

ChristianW (talk)11:42, 28 November 2018

An article exists at w:Webhook. It's a rather technical term, usually directed only at developers. In a specific application, it might have a more specific meaning which can be conveyed by other words, but a generic translation in French may not exist yet.

Nemo (talk)11:47, 28 November 2018

Great! thanks !

A webhook in web development is a method of augmenting or altering the behaviour of a web page, or web application; Webhooks are "user-defined HTTP callbacks".

So I will propose something like "point d'ancrage web" for FR in extenso translations.

ChristianW (talk)12:31, 28 November 2018

A common translation for “hook” in web development is “crochet” (see for example) or sometimes “point d’entrée”.

“point d’ancrage” is a mix between the both translations, maybe a pretty good idea.

Depending of the context, we may use English word “hook” which is well-known (and commonly used) by all developers.

“web” should indeed stay “web” in French.

Pols12 (talk)15:59, 28 November 2018

Spelling mistake in MAZI:portal-admin.general.reboot-modal-message/en


I was translating MAZI Zone and I noticed that in MAZI:portal-admin.general.reboot-modal-message/en, there is word 'minutres' which should be minutes.

Pyscowicz (talk)10:22, 26 November 2018

Requesting activation of Seereer and the Cangin languages, and translator rights


Would you kindly:

(a) activate the Serer — Seereer language (language code: srr), LTR (written from left to right); For MediaWiki, first fallback to French, 2nd English
(b) activate Saafi-Saafi — Saafi-Saafi (code: sav), LTR. For MediaWiki, first fallback to French, 2nd English
(c) activate Lehar — Laalaa (code: cae), LTR. For MediaWiki, first fallback to French, 2nd English
(d) activate Noon — Noon (code: snf), LTR. For MediaWiki, first fallback to French, 2nd English
(e) activate Paloor, Palor — Sili-Sili (that's the proper name, also known as Paloor / Palor, code: fap), LTR. For MediaWiki, first fallback to French, 2nd English
(f) activate Ndut — Ndut (code: ndv), LTR. For MediaWiki, first fallback to French, 2nd English
(g) enable all above languages in the Latin alphabet
(h) I would also like to request translator rights here for all

Many thanks,

Tam (Tamsier)

Tam (talk)06:54, 19 November 2018

Block "BadDog"

Someone should block user "BadDog". Makes bad translations in sr-ec and not translating sr-el.

Obsuser (talk)14:42, 19 November 2018

This does not make any sense. I'm not making bad translations. I have the feeling that when you make a translation, you think that it is just yours. And when someone changes it, you immediately undo that edit, regardless of whether it is valid or not. Also, you translate text with some non-existent words such as "Клипборд" и "валидан", but Microsoft and Google terminology don't have such translations (example: 1). The style of your translation does not coincide with the established style of translation in Serbian. You make up your own words instead of looking at Microsoft or Google terminology. Not to mention that you translate word by word somewhat instead of adjusting and, if necessary, shortening the translation. Sr-ec translations are automatically importing using Zoranzoki's bot. Rancher also has a remark on this user. You're not even a regular translator at all. Instead of having to deal with making new translations, you report regular translators for blocking. In fact, you do not intend to do it at all, you only profane a translation project in this language… No comment.

BadDog (talk)18:26, 19 November 2018

I need to revert most of your translations and often find Watchlist full of bad edits by that account. That's why it should be blocked from editing.

Obsuser (talk)23:51, 20 November 2018

You are reverting my changes because you think your translations are the most perfect. But when someone changes them, you are acting like a primadone, and then you undo that change (regardless of whether it is valid or not). Bad edits, umm? Give my latest change you reverted for example (1). My version: "Сматрај ниску за претрагу као регуларни израз". Your version: "Поступи са стрингом за претрагу као с регуларним изразом". Term "Treat" shold be translated as "Третирај" or "Сматрај" (Microsoft). Term "Поступи" is closer to "act", and have that meaning. Term "стринг" doesn't exist in Serbian. The word "ниска" clearly established on most of our translations projects. Microsoft are using it (1). Unfortunately, I did not find translations from Google Help site, but I also found that site (open source projects terminology in Serbian) to make sure of the translation "ниска".

+ Deletes the terminology from the portal

Have a nice day! / Goodnight!

BadDog (talk)00:19, 21 November 2018

They are.

Obsuser (talk)20:03, 21 November 2018

Πληρωμή Μεταφράσεων στους Συνεισφέροντες στο

Γεια σας! Είμαι νέα σχετικά μεταφράστρια στο, KATRINE 1993,παρακαλώ ενημερώστε με στο email,αν οι μεταφράσεις σε αυτήν την ιστοσελίδα του Wikipedia πληρώνονται στους μεταφραστές, οιαδήποτε τιμή, ΘΑ ΣΑΣ ΗΜΟΥΝ ΕΥΓΝΩΜΩΝ για οιαδήποτε απάντηση. ΕΥΧΑΡΙΣΤΩ εκ των προτέρων

K.Katapodi13:49, 19 November 2018

Cantonese disappearing everywhere in translatewiki

Not sure if it's the translatewiki's fault (scanned the Translate extension commit history but found nothing), but since the new statistics tables are implemented, the Cantonese (yue) has disappeared from the message group statistics but not from the language statistics. Also, Cantonese is since then missing from the UniversalLanguageSelector. And in Special:Translations, the label "Cantonese" is now replaced by "yue". This has really caused some inconvenience.

Hello903hello (talk)07:22, 10 November 2018

It's not related to the statistics table. Can you confirm it is fixed now?

Nike (talk)17:42, 14 November 2018

Yes, it appears to be fixed now.

Hello903hello (talk)08:23, 15 November 2018

Fallback language of kjp (Eastern pwo)

Some untranslated messages of kjp are now showing in bo (Tibet). The fallback language of kjp should be Burmese (my). Please check.

NinjaStrikers «»05:02, 13 November 2018

Permissions error in saving translation

I am unable to save the translation for MediaWiki:Copyright/gom-latn because of the following error:

Saving the translation failed: You do not have permission to edit this JavaScript page because it may affect all visitors. Permissions for editing of sitewide CSS/JS/JSON files were recently separated from the "editinterface" right. If you do not understand why you are getting this error, see mw:MediaWiki_1.32/interface-admin.

If you would like to save it yourself, the translation for this message is:

Mozkur $1 hachea khala uplobdh asa kheriz her nondi kelea xivai.

The Discoverer (talk)22:08, 7 November 2018

I saved it for you.

Nike (talk)15:26, 8 November 2018

Thanks! :)

The Discoverer (talk)16:20, 8 November 2018

LibreRouter: new project with software and HowTo booklets

Hi, we're curious about whether TranslateWiki might be a good home for the translation of a project we're working on, the LibreRouter. We want to translate software interfaces, documentation, and also an illustrated booklet about how to use the LibreRouter. There's more info about the project at

The code is in the repositories at, and is in English. All the software is in active development or pre-development. One of the apps in active development that's already giving attention to translation is

The source language for the HowTo booklets is Spanish. The text for those booklets isn't ready to translate yet, though we hope to have first drafts ready no later than mid-October.

Some people from our community would join the translation effort, especially for English, Spanish, Portuguese, and maybe German and Afrikaans.

We've tried the interface for translating software strings on TranslateWiki, and we like it. We're not sure if the format of the HowTo booklets is compatible with TranslateWiki, since those are long paragraphs of text. We tested on Zanata, and it worked with .ODT files.

If we need to use a different file format for the code i18n/l10n or for the booklets, we're open to that.

We're interested in TranslateWiki because of the community of translators already active here, and the long-term continuity of the TranslateWiki platform and community.

Does this look like a good match, LibreRouter with TranslateWiki? What would be necessary or desirable actions from the LibreRouter community in order to move forward? We're available to chat on IRC or via e-mail or here on this thread.

Pato (talk)15:05, 21 September 2017

Hi TranslateWiki team,

I wonder how to get in touch with you so that we can figure out whether LibreRouter can join TranslateWiki. I don't see any email address to write to, and the IRC webchat isn't working at the moment (and I don't usually spend any time on IRC). I will respond here to the items listed on the New Project criteria page, and hopefully this will make it clearer whether LibreRouter can join TranslateWiki.

- Openness: yes, LibreMesh software and documentation use free and open source licenses, such as GPLv3.

- Development: yes, LibreMesh is in active development, using a Git repository for version control. The project has periodic releases of LibreMesh, and will have periodic releases of other software and documentation (which has't yet reached first release). Time to get translations into use is currently unknown, and depends on how often network maintainers update the firmware on their router (perhaps we could automate part of this process to make TIU faster, or have a translation-only auto-update so as not to deal with potential software bugs and version incomatibilities between routers on a network), and how often users update Lime-App on their phones. More discussion could be helpful.

- Integration: It seems very reasonable that TranslateWiki staff could have direct push commit access.

- i18n Support: two key parts of the LibreRouter system support i18n already (LibreMesh GUI and Lime-App), though I do not know if they support the details of i18n mentioned on the TranslateWiki New Project page. I have passed the Localization for Developers link to developers and they're looking at it.

- Communication: I am the current liason, and I am not active in development. I have communication with the developers, and it's feasible that one of the developers may takeover the liason role and/or at least one developer might be active in I am a user and tester of the software and documentation.

- File formats: yes, we use translation files, I don't know if they're in one of TranslateWiki's preferred formats. Here's a translation file for Lime-App , and I'll find one for LibreMesh.

We need to start translating this month, October 2017.

What else do you need to know in order to decide whether LibreRouter can join TranslateWiki?

cheers, Pato

Pato (talk)20:35, 6 October 2017

The JSON format looks okay except we don't include the language code as a key in the file (it's already there in the filename). Would you consider changing that format?

Is the repository in GitHub your main repository?

I would request to add some message documentation to guide the translators (see

Nike (talk)20:45, 6 October 2017

Does taking the language code as a key out of the file just mean removing the line   "es": { As well as the closing bracket } ?

Yes, the repository in GitHub is our main repository.

We will add some message documentation to guide the translators based on the advice at It might take us a week or so to start adding that documentation.

Pato (talk)21:03, 14 October 2017

Yeah if the file looks like following, then we support the format.

  "key": "value",
Nike (talk)14:10, 15 October 2017

I'm talking with coders... we're moving forward on changes to be more compatible with TranslateWiki, and we're coming up with questions about TranslateWiki:

1) We're looking at 4-7 different pieces of software to translate. Each piece has it's own practices of what branch development happens in, so we're getting all that info in one place. Arranging direct push commit access for TranslateWiki to the development branch of each software is part of our conversations.

2) If one or two pieces of software are ready to connect with before the others, can we go ahead and connect those? If yes, how?

3) Can the platform translate the file for each software? Or maybe we'll have to setup a separate help folder with a file in each language, like at -- would that work? Is there a parser-generator for MarkDown .md files?

4) Is there a smartphone interface for, either via a web browser or a special app? (It seems that using a computer with a keyboard and at least a 10-inch screen is easier for translating, but sometimes a smartphone is the only device available to a translator.)

5) How do we include screenshots in the translator notes (the qqq messages)?

Pato (talk)03:29, 11 November 2017

1) Are those pieces in different git repositories?

2) Yes we can. I need the basic info about the repository, push access, file format.

3) We do not have MarkDown parser at the moment. It could work as translatable page.

4) Amir is working on a Telegram app. There is also unmaintained android app. The web interface should accommodate tablets pretty well, but mobile phones are not well supported.

5) Uploading them here in and using the wikitext syntax to include them. Can also put direct links to images, if they are too large, but then translators have to click.

Nike (talk)15:24, 12 November 2017

1) Yes, each piece in a different repo.

2) The first two pieces that I think are ready:

3) "It could work as translatable page." Do you mean it could work without a parser?

4) Cool! I hope Amir and crew get that Telegram app to a usable release.

5) Where in TranslateWiki would we upload the screenshots? When you say "too large", what are the maximum dimensions of the image (like 80px by 200px)? What is the maximum file size?

Pato (talk)23:22, 13 November 2017

6) Where is the code for the parser-generators that are currently in use on We'd like to look at them to get a sense of what it would take to write another.

7) Any suggestions on how to internationalize this relatively simple web page interface, ?

Pato (talk)14:36, 12 November 2017
Nike (talk)15:26, 12 November 2017

6) Thanks, we'll look at those.

7) The maintainer of the software to internationalize (Chef) says: "I'm currently not using jQuery in Chef but plain JavaScript. I'd rather keep it that way - if possible. Some quick searches resulted in - maybe thats already enough?"

Pato (talk)23:23, 13 November 2017

Also, what are the howto booklets you mention in the subject? Our primary focus is on software user interfaces. [edit] We don't currently support ODT files. Some kind string extraction to another format would be needed. Are the booklets created so that they can be automatically generated from the translated texts (i.e. no hardcoded positionings with length restrictions)?

Nike (talk)20:46, 6 October 2017

The HowTo booklets are a series of guides about the social, technical, and economic aspects of how to create and maintain a community network, with the LibreRouter as the example hardware and software. The idea is that each booklet will be laid out by hand after translating. This means that an automated workflow (as is used in software) is not our plan for the first three languages, and we would join only for the software interfaces.

However, if anyone can suggest a workflow to create the booklets that aligns with the way functions, we're interested to try it out since that could facilitate the translation of the booklets into many more languages. Perhaps the ODT parser from the Zanata translation management platform could be included in, or perhaps we could use a different format. Or perhaps a bit of the BookType software used to create the books at could be reused.

Pato (talk)21:22, 14 October 2017

I haven't done that before. I am sure there are string extraction plugins for ODT. The problem is that usually booklets have quite tight positioning and size constraints. Doing the layout manually for many dozens of languages (and dealing with possibly frequent updates) doesn't scale. But a flexible or simple ODT file we could probably support if there is a suitable parser-generator we can integrate.

Nike (talk)14:29, 15 October 2017

Hi Nike, any chance you can setup the repo for LibreMesh document translation this week? Following the thread at

Pato (talk)19:49, 4 November 2018

This has been continued in chat discussions.

Nike (talk)15:23, 6 November 2018

Request for rights (Zoranzoki21)

Hi, can you give me back offline translator right, so I no need each time to use bot for it?

Too, give me translation administrator right so I can manage translations. Thanks!

Zoranzoki21 (talk)09:21, 2 November 2018

Done Done

For translation administrator, please contact a staff member.

\m/etalhead 12:29, 5 November 2018


Zoranzoki21 (talk)19:08, 5 November 2018

Problem with publishing translations

I can't publish translation due the error.


Translating error.png

Is that normal? It's a translation, not a Javascript page or something…

BadDog (talk)12:23, 3 November 2018

A handful of messages (5) are not currently editable. This is one of them. If this doesn't resolve itself over time, I will lift the restriction.

Nike (talk)15:20, 3 November 2018

#Babel translations for muiwiki in Incubator

Someone has translated some messages on #Babel to the Musi language. However, the translations do not seem to appear on the Babelbox in Incubator nor in Meta. Any idea? Thank you in advance.

NoiX180 (talk)03:55, 1 November 2018

Please see FAQ#How_is_the_work_done_on_translatewiki.net_connected_to_other_wikis?. The translations were made today.

In addition LocalisationUpdate is currently not running, so translation updates get deployed to the sites only once per week.

Nike (talk)15:36, 1 November 2018
First page
First page
Last page
Last page