View source for Thread:Support/Message info please/reply (8)
I think it will be good idea to add GENDER support for the word "user" to the following messages, unless technical restrictions make it difficult like in the case of:
- ("There is no email address recorded for user "$1".")
- ("User is blocked")
- ("This user is currently blocked.
The latest block log entry is provided below for reference:")
- ("You do not have permission to edit this page, because it contains another user's personal settings.")
- noemail: done in mwr:66933
- Blockedtitle: I think this message may be incorrect, and may have to be rephrased. It is used in OutputPage::blockedPage(), which has the following documentation: "Produce a "user is blocked" page.". I may be wrong, but not making changes here now.
- Blocked-notice-logextract: GENDER already supported. Documentation updated.
- Customcssjsprotected: Because of code structure, adding GENDER support here would be more complex than we would really like. Not changing.
Should be changed to "reason" for consistency with other similar messages and to not make it sound that optional. One should generally always write a reason for why to revert a file.
Should use GENDER support, for example it's common in French to use different adjective endings depending on one's gender. Thanks.
I came here to tell you that the interface of Uyghur Wikipedia is still in Uyghur latin. Could you please switch it to Uyghur Arabic because the majority of Uyghurs prefer using it instead.
Both versions do not have their "most wanted" messages done but the Arabic version is the one best developed.
I would propose that we make the change if there is substantial effort in localising it (in either of the localisations). For now about 30% of MediaWiki has been localised in the Arabic script, and 5% in the Latin script. Neither localisation has had any contributions in the past 200 days. Please help us address that first, Jose.
There have been substantial effort in localising the Uyghur arabic interface messages, especially during the period from May 16 - 22, as could be seen here. This means that only 32 (1.3%) out of 2421 messages need to be localised.
Is there also a requirement that the Uyghur Latin version also needs to be localised before Uyghur Wikipedia interface is switched to the Uyghur Arabic script?
"Take Me Back" should be changed to "Take me back" because of the proper capitalization and for consistency with. Thanks.
Converted a few tables from MyISAM to InnoDB. Took a while for some tables, causing the wiki basically to be read-only, and lighttpd to serve some '500' errors.
ALTER TABLE `bw_text` ENGINE = InnoDB; 5 min 45.90 sec */ ALTER TABLE `bw_archive` ENGINE = InnoDB; 54.54 sec */ ALTER TABLE `bw_logging` ENGINE = InnoDB; 1 min 22.49 sec */ ALTER TABLE `bw_watchlist` ENGINE = InnoDB; 21 min 48.14 sec */ ALTER TABLE `bw_templatelinks` ENGINE = InnoDB; 4.37 sec */ ALTER TABLE `bw_pagelinks` ENGINE = InnoDB; 25.69 sec */ ALTER TABLE `bw_categorylinks` ENGINE = InnoDB; 0.91 sec */ ALTER TABLE `bw_externallinks` ENGINE = InnoDB; 12.14 sec */ ALTER TABLE `bw_imagelinks` ENGINE = InnoDB; 0.28 sec */ ALTER TABLE `bw_revision` ENGINE = InnoDB; 1 hour 44 min 57.29 sec */
Two tables to go, will try and find a faster solution for those...
ALTER TABLE `bw_page` ENGINE = InnoDB; /* 1 hour 10 min 33.22 sec on test db */ ALTER TABLE `bw_recentchanges` ENGINE = InnoDB; /* 54 min 50.80 sec on test db */
("Auto-review: requires "$1" permission"): Should it say "requires" instead of "require"?
The following messages should have been fuzzied:
- ("Revision cannot be reviewed with some fields left "inadequate".")
I have added a draft FAQ on ensuring consistent localised terminology. Is what I have written good sense? Is there anything which could be usefully added on this topic? Is there a help page where this section could be usefully copied?
Also propose putting links on each project page to glossaries on the project websites, if available, as resource to translators.
What does the message("Leaving system message.") mean?
And the message("System messenger")?
- Usermessage-summary : the edit summary for a system message
- Usermessage-editor : the user that is the editor of system messages
Any message that is posted because of a system event - whichever you can think of. Currently only a failed asynchronous upload is notified as far as I know.
Wikia:Founderemails-email-3-days-passed-body-HTML/en: should have a comma after $FOUNDERNAME like this "$FOUNDERNAME,".
Could someone use a bot to replace all "voltar" with "volver" for all Galician (gl) messages? Thanks you.
Done -- btw, for the 31 changes made, this wasn't really worth the effort of extracting page names from the database, renaming namespace IDs to namespace names, and configuring the bot (~25 mins of work). Please make an estimate of how many changes will have to be made, and if it is in the tens, please do not make a bot request, but see if you can do it manually.
Sorry, but there are still many massages containing verb "voltar" which remains unchanged.
Wikia:Multilookupnbrresult/en (Number of results:): it apperas that this should say "results" instead of "result". Anyone able to confirm?
Wikia:Multilookupnotspecify/en (You have not specified an IP address yet.): "a IP" should be "an IP".
After a long discussion at  we decided to migrate ro.wp from s/t-cedilla (ţ, ş) to s/t-comma (ț, ș). I have changed the namespace names at , but we need the old names to be kept as aliases.
Below is a list of standard namespaces with the _OLD_ spelling. They need to be used for _ALIASES_:
3: Discuţie Utilizator
5: Discuţie Wikipedia
7: Discuţie Fişier
9: Discuţie MediaWiki
11: Discuţie Format
13: Discuţie Ajutor
15: Discuţie Categorie
In addition to that, there are 2 more namespaces specific to the Romanian Wikipedia which need to be converted (from the form on the left to the form on the right):
101: Discuţie Portal -> Discuție Portal
103: Discuţie Proiect -> Discuție Proiect
A bugzilla bug with the same request exists  and should be closed after making the changes.
Thank you for your help.
Linked to the request above, I want to ask you if there is anyone able and willing to run a bot to replace ţ,ş with ț,ș in all the Romanian translations. This needs to happen at a later time, after all the preparations are finished on ro.wp.
Please give me a ping when preparations are finished. Then I will export the changes from translatewiki into SVN. The day after my export it will be live on all Wikimedia projects.
I have just reactivated 'ro' in the MediaWiki export, so Raymond will most probably automatically export the Romanian updates later today, if he remembers to use the correct export window :).
I'm afraid it is still too early. Please hold on until we can have all the preparations finished - I estimate another week or so.
Explicitly refer to Wikimedia Commons, what is Wikimedia projects centric. Will be issue for independent shared repository installations.
This feature was available at the old edit boxes, at the new pop-up ones it doesn't...
Whenever I try to edit translation the edit box is LTR aligned by default and I can't change it (using Chrome, Firefox and IE does support that)
Also the suggestions appear as LTR even if they are RTL I use suggestions from Arabic and Google translation, they both appear to the opposite direction, if there's English somewhere in the string the text gets all mixed up and that's a shame...
I can send screenshots or stylesheet for Stylish to demonstrate my complaint